In the new versions of System Center, updates are intelligent. For example in SCCM all product and feature updates are automated (https://msincic.wordpress.com/2016/03/24/new-feature-of-system-center-configuration-manager-1511-updates-and-updates/).
In the case of System Center Operations Manager one of the problems was that updates to Management Packs have to be manual through monitoring of product blogs.
The new feature of Updates and Recommendations lists Management Packs that had update and allows with the button Get All MPs download the updates automatically:
A good news to the Administrators group of SCOM!!!
What is the SCCM 1511 and when they will leave SCCM 2016?
Before I talk about this new feature, it’s good to remember that now the SCCM year as version (2007, 2012, etc.) and will be like Windows 10 using a build and we are currently in 1512 in RTM (not test version).
This is good news, because the concepts of version that hinder the licensing and maintenance. Even better with the new feature that we can talk now.
What is the Update and Servicing?
One of the news involving the System Center Configuration Manager’s console update 1511 "Update and Servicing".
This new functionality could be complemented with this feature (https://msincic.wordpress.com/2014/07/16/configuration-manager-servicing-extension-for-sccm-2012-sp1-and-r2/), but now has moved on.
From that new item in the console it is possible to know which version is the Build in production and to download and install as if it were Windows Update to SCCM.
In the example below you can see that downloaded the update from 1511 to 1512 without any intervention during the download and installation, coupled with the fact that he automatically do the rollback on failure:
It is interesting to note that it is now possible to download only updates features in the Update and Servicing, which was not possible until 2012 SCCM R2.
With this news coupled with the fact that we don’t have more complex versioning, it will be much easier to maintain in SCCM.
It is common to install SCCM in its various versions leave to put the key after the evaluation.
However, in 1511 version released in late November the common option being used doesn’t work anymore, i.e. use the Setup option in "Perform maintenance site or reset this site":
However, note that it appears the option to include the installation key:
This "problem" is most likely a bug or some intention not yet defined after 60 days the SCCM 1511 passes to no longer give the option of using the key.
To rehabilitate, it’s important to know that the problem is a change in the key HKLM\Local Computer\Software\SMS\Setup where the Product ID is changed to "NONEVAL", which prevents the insertion of the key after installation:
To resolve this problem, simply change "NONEVAL" to "EVAL", close Regedit and rerun the Setup:
Voila!!!! We can now include the key!
One of the news in the System Center "2016" TP4 is the end of the use of SharePoint for the self-service portal.
It was a constant complaint, both because of the need for creation of SharePoint, Layout, administration and the 2010 version that was required. In general we were forced to install a SharePoint Foundation 2010 server on Windows 2008 R2 to serve as a portal with all the implications of another service and server being administered.
In the new version TP4 available for download is already available the portal completely in HTML! (https://technet.microsoft.com/en-gb/evalcenter/dn781241.aspx)
For the 2012 R2 version was also made available the portal within the Update Rollup 8 2012 SCSM R2 in https://www.microsoft.com/en-us/download/details.aspx?id=49556
Here are some of the main screens and how much more simple, functional, visual appearance and layout of Windows 10 and with the quick access buttons on the top bar on the entry screen of the portal:
When opening a call, the data is the same but now we can indicate what the "favourites" to appear on the portal, in addition to being able to customize for each user:
Finally, the interaction with the media has become much more pleasant and with the quick access buttons on the top bar easier to check for updates.
Anyway, this is a novelty that the much expected and finally became available in version TP4 and 2012 R2.
A recurring problem that we have now several customers started to use the Storage Space to mount volumes RAID is he not return mounted when the machine is restarted.
Every time a server you have configured disks from Windows Storage Spaces, 2012 is necessary to go in and redo the Volumes Attach the disc.
In Server Manager, configuration of volumes of Storage Space below, in the column of warnings appears a warning yellow, indicating that the disk is okay and you do right click to Attach and he returns to appear on the server with the same configuration and letter originally defined.
When a Storage Space is mounted, one of the options that can be set by the PowerShell (is automatic in the GUI Server Manager) is the IsManualAttach that must be True.
When the disc is moved from one server to another or redefined by adding the Manual Attach disk returns the pattern that is False.
The solution is very simple, use the PowerShell below to list the volumes that are as: manual
Get-VirtualDisk | where IsManualAttach
Will be generated a list as copied below, where you can see that the IsManualAttach is enabled:
Using the name of the disk, which is the name that appears in Windows Explorer, you can disable the attach manual:
Set-VirtualDisk-FriendlyName RAID-VMs-IsManualAttach $False
Dell has two very interesting tools to integrate with SCCM.
The first is the Dell Command | Set that allows you to create executable files to configure your company’s desktops and notebooks. Available at http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7532.dell-command-configure
The second is the Dell Command | Warranty that brings online warranty data, customer service and purchase of each equipment registered in SCCM. Available at http://en.community.dell.com/techcenter/extras/m/mediagallery/20441033/download
Dell Command | Configure
It is necessary to have standardized security companies, specific options on the machines or standardization of features. For example, enable PXE, TPM, BIOS change password, boot order, power saving options, disable HW features (plates, USB, eSata) and any other existing options in the BIOS.
This tool is very simple to install and use, as can be seen the main screen of the authoring console, the settings options:
- Create a package for any equipment which may be non-existent options in all the company’s equipment
- Create a package based on equipment location, where only what is the template that is being used for the console appears, useful when all equipment are standardized
- Open a package already created to edit or clone
- History of the packages created, edited and exported
To start creating a package simply click the Edit button and select the desired option:
In this case I set the boot order of the machines to avoid it being used the DVD or USB as primary boot. Note that the console have the Add Device button that allows you to configure all kinds of device, in the desired order.
After the edits, just click on the button Export Config to save the package in order to then be able to change it or Export. EXE to generate the executable and the sh file containing the metadata to be imported into the CONFIGURATION MANAGER:
Soon after generating the executable, the next step is in the SCCM console use the Import button Dell Command | Configure Package as the image below shows. Important to remember that the two folders within Packages are created by the installer:
Once created the package, unless the executable and imported into SCCM the process is just like any other package, making the Deploy to the collections that you want to configure the BIOS.
To download and install the Dell Warranty it creates a shortcut that opens a command window, since the tool has no graphical interface from Dell. Below includes the graphical tool link from Microsoft available on TechNet Library:
Note in the window above the first command serves to indicate where is the data through the SCCM database. Below the DellWarranty-CLI command makes the link to the SCCM database:
In the sequel we can ask for the utility with the command DellWarranty-CLI bring all warranty data, as the image below demonstrates with the result in CSV:
Can be seen in details such as type of purchase, complete model, guarantee, warranty and service, etc.
With the Dell Warranty Extension tool available in https://gallery.technet.microsoft.com/Dell-Warranty-Status-20-ae67cc13 you can view this data by right-clicking the equipment:
Gartner has released in the middle of last month the new quadrant of hypervisors x 86.
In relation to the previous quadrant highlights the gap between VMWare and Hyper-V compared to other products
In the case of Microsoft Suite Gartner highlights the integration of System Center with Hyper-V and Azure for hybrid clouds, but recognize that System Center has superior features in relation to managing the it environment as a whole.
To read the full report click http://www.gartner.com/technology/reprints.do?id=1-2JFZ1KP&ct=150715