Thanks to Jesse Walter, I now have an easy way to do a Java silent install and update Java with SCCM. I tested this today at a customer and it worked very nicely. Whenever a new version of Java is released they can now quickly update their SCCM package without any hassle.
Deployment took an extra restart after selecting which task sequence to use. This happend because multiple task sequences where published to the computer and the boot image for the selected task sequence where not used initially when booting.
I fixed this by making the task sequences use the same boot image. I know this might not be the ideal solution for everyone but the problem with this extra reboot is different version of bootimages beeing used.
This is how you upgrade from evaluation version to full version of configmgr 2012. You enter the product key during the install phase of configuration manager 2012.
- Run configuration manager setup from the start menu. This ensures that setup is run wil the latest updates.
- Select perform site maintenance or reset this site.
- Select Convert from Evaluation to Full Product Version and enter the key.
I had a weird problem with a customer during deployment of Windows 7. Deployment of the image went fine but during the phase “Setup Windows and Configuration Manager” I would get the following error message: TSMBOOTSTRAP.EXE The program couldn´t start, becuase ccmcore.dll is missing. Read More
Today I did some work for a customer who had already installed configuration manager, but they had not set up deployment. I enabled PXE on the distribution point but the clients did not get a repsonse when trying to pxe boot. The first place I check is the SMSPXE.LOG to see what happends but the file did not exist.
The new server manager in Windows Server 2012 can also manage Windows Server 2008. This is how you set it up in 3 simple steps:
Windows Server 2008 with SP2 and Windows Server 2008 R2 with SP1
- Install .NET Framework 4.0 (Download from Microsoft)
- Install Windows Management Framework 3.0 (Download from Microsoft)
- Run the following command in powershell to enable and configure Windows Management Framework “winrm quickconfig“
MDT 2012 Deployment Workbench on Windows Server 2012 will fail with the following error: “powershell is required to use the deployment workbench” The reason for this error is the execution policy in powershell.
Solution: Run the following command from powershell Read More
Microsoft have released a nice tool which help you create WMI queries. WMI Code Creator 1.0 is a powerful tool to create WMI queries without little or no programming skills. I use this frequently to retrieve the model name from computers that I need to target specific driver packages.
My colleage at Atea, Oddvar Håland Moe, have written a script that dumps the password of the network access account from the boot image in plain text. This is why you never enable command line support in your boot images on a production network. Anyone will be able to retrieve the password during PXE boot / OS deployment. Read More
When I first heard about this neat trick I thought it was a joke. But it’s not. It works and it’s awesome. GodMode is a special control panel that includes all windows settings from one windows. No more jumping between several windows to do stuff.
How to enable God Mode in Windows 8, Windows 7 and Windows Vista.
These log files are useful to troubleshoot the errors with the configuration manager client.
Log files on server.
- ccm.log – Client push installation log file.
- chmgr.log – Client health manager log file.
- cidm.log – Changes to the client settings by the Client Install Data Manager (CIDM).
Log files on client.
- ccmsetup.log – Installation, client health, client upgrade and client removal. Very useful to troubleshoot client installation errors.
- ccmrepair.log – Repeair activites by the client.
- client.msi.log – Logs from the installation process of client.msi application.
Also check out this TechNet article for more information about log files sin System Center Configuration Manager 2012.
When you install a distribution point, you specify which drive it should use. When this drive is full, the distribution point will automatically start using another drive.
For drives where you don’t want any packages from the distribution point, create an empty file with the name “NO_SMS_ON_DRIVE.SMS” and place it in the root of the drives.
This trick works on both SCCM 2007 and SCCM 2012.
In this guide for System Center Configuration Manager 2012 I will show how to create a limiting device collection structure. We start with All Systems as root, and create one collection for all servers and one for all workstations.
Windows 8 is getting closer release. One of the new cool features I look forward to is Windows To Go. It is Windows 8 installed on a usb stick and works as a live-usb installation. This can be used to test Windows 8 in your environment without messing up your installation. But it has much more potential than that.