In some cases, you may want to set a fixed screen resolution for all clients. Then you will have the Challenge with the Picture was not scaled to fit the monitor. In my case, it was due to a Intel driver setting. I found no registry setting, no documented API or command line reference, so as a last measure I had to use keyboard shortcuts, as the Intel software listens for ctrl + alt + f11 to change monitor scaling. I created a simple script to find the Intel video adapter in WMI and used sendkeys to utilize the keyboard shortcut. This script must be run at user log on.
set WshShell= WScript.CreateObject(“WScript.Shell”)
‘Connect to WMI
Set objWMIService = GetObject(“winmgmts:\\.\root\cimv2”)
Set colItems = objWMIService.ExecQuery(“Select * from Win32_VideoController”)
‘Get Video Card
For Each objItem in colItems
VideoCard = objItem.Description
‘Check if VideoCard is Intel then Send Ctrl + Alt + F11
If VideoCard = “Intel(R) HD Graphics” then
Set colItems = Nothing
Set objWMIService = Nothing
If you struggle to read the official documentation and identify witch ports to open for System Center 2012 Configuration Manager.
Odd-Magne Kristoffersen has done the job for everyone and created a Excel spreadsheet documenting all the ports.
Please read his blogpost and download the spreadsheet.
Microsoft Documentation: http://technet.microsoft.com/en-us/library/gg682180.aspx
If you are about to invest in new or re-use old hardware, a good tip is Microsoft’s compatibillity center. Chanses are you will get answers there about Windows compatibillity.
SCCM will Return System Error Codes from failed Application installations. Microsoft have published the complete list With for Developers for troubleshooting purposes.
Example Return codes:
- 1633 (0x661) – This installation package is not supported by this processor type. Contact your product vendor.
- 1603 (0x643) – Fatal error during installation.
Complete list: http://msdn.microsoft.com/en-us/library/windows/desktop/ms681381(v=vs.85).aspx
In some cases you may have to run a script or application after completion of your task sequence. In my case this was related to pre-staging of applications (more of this later).
Anyway Michael Murgolo have written a great blogpost describing how to implement this. If you are not in a hurry i recommend you to wait for SCCM SP1 RTM then you will have this included.
If you are in a hurry like me..
Using System Center 2012 Configuration Manager together with the MDT integration and the new UDI wizard I discovered that using comma (,) in the application name will cause the deployment to break.
Make sure the application is marked for dynamic app install Policy download failed, hr=0x80004005. The operating system reported error 2147500037: Unspecified error
Working with SCCM 2012 I got this message and was unable to edit a application. Some solutions online suggests you to alter the database. This is the last resort first try this:
Stop the SMSEXEC service on the server. You will get access to the package. Then start the service again.
If you have been using SCCM 2007 and now SCCM 2012 for a while you may see that your deployment time has increased, if you used the “Access content directly from distribution point option” in SCCM 2007.
Microsoft introduced the new content library, the idea is to save space by saving all files in a library but only save identical files once, and refer to the location for all other instances of the file. The idea is good, but it comes with a price. All content stored in the library must be extracted during installation. This slows down the deployment meaning all files will have to be downloaded by the client.
If you want to change this and store your content in a share, you can. Please be aware that this has a cost in disk space.
On all your content in the task sequence meaning packages, boot, images, drivers even the configuration manager agent, select “copy the content in this package to a package share on distribution points.”
After doing this you will be able to select “access content directly from..” on your deployments.
This limits you to use the old package model. So you have to decide what’s most important to you. A workaround could be to use the MDT integration for installing apps. Then you will have the best from both worlds.
Microsoft has released a whitepaper where they compare private cloud solutions from Microsoft and VMware. If you are curious about private cloud technology and what Microsoft has to offer, i recommend reading this whitepaper.
Download it her: http://download.microsoft.com/download/F/3/6/F36D9AE8-6238-4EA3-9ABC-BF7BB848BF70/MicrosoftPrivateCloudWhitepaper.pdf
Want to deploy Windows 8 and Server 2012 with SCCM, start the preparation in your test/lab environment now!
- Deployment and management of Windows 8 and Windows Server 2012
- Distribution point for Windows Azure to help reduce infrastructure costs
- Automation of administrative tasks through PowerShell support
- Management of Mac OS X clients and Linux and UNIX servers
- Real-time administrative actions for Endpoint Protection related tasks
If you are spending most of your time on the HP driver download page, installing, testing and importing drives into SCCM. Please take a look under the “Software – System Management” node. Chances are HP already did the work for you 🙂
I have created a simple vbscript that can be useful in agent migration.
- Notify user, display popup (click ok to start installation now or wait 5 minutes)
- Install SCCM 2012 Agent
- Wait for installation to complete
- Notify user (installation completed)
- Reboot client to complete installation.
get the script here
Great case study by Cameron Fuller regarding using a common SQL for multiple SC 2012 products.
Included updates to System Center 2012 for compatibility with Windows Server 2012 Release Candidate including support for Azure VM and capabilities for Hosted Service Providers.
If you experience a server crash and you are not able to do a proper uninstallation, SCCM will have some components left on the SQL server. Please read this blogpost for more details.
In my recent expirience i found out that installing a local SRSS instance on a SCCM 2012 server configured with it’s database on a remote sql cluster will break the authentication between the SCCM server and the SQL. Site repair or uninstall will not work due to lost DB connection and you may have to reinstall the entire site.
The System Center 2012 Configuration Manager SDK provides information applicable to administrators who want to automate Configuration Manager through script and to developers adding features and extensions to base Configuration Manager functionality.
If the deployed client ends up with a MINNT name after using the “import computer information” assigning name and mac address.
Take a look at this blog post: http://blog.coretech.dk/mip/wrong-pc-name-after-deployment/
or this one:
Service Pack 1 for SCCM 2012 is announced. This updated includes Windows 8 support (as expected) but also support for Linux and OS X.
Read more here: http://blog.coretech.dk/kea/configmgr-2012-sp1-announced-teched-2012/
If you get this error: Cannot connect to the application server. It may be because you are missing WCF activation.
- Start Server Manager > Features > Add Features > .NET Framework 3.5.1 Features > WCF Activation > HTTP Activation.
- Open Command Prompt (start > run > cmd)
- CD %windir%\Microsoft.NET\Framework64\v4.0.30319
- run: aspnet_regiis.exe /iru
Free E-book from Microsoft press. Great book to get a better understanding of the Windows 7 deployment platform.
Chapter 3 Deployment Platform . . . . . . . . . 85
Chapter 4 Planning Deployment . . . . . . . . . 113
Chapter 5 Testing Application Compatibility . . . . . . . . . 139
Chapter 6 Developing Disk Images . . . . . . . . . 179
Chapter 7 Migrating User State Data . . . . . . . . . 223
Chapter 8 Deploying Applications . . . . . . . . . 247
Chapter 9 Preparing Windows PE . . . . . . . . . 273
Chapter 10 Configuring Windows Deployment Services . . . . . . . . . 293
Chapter 11 Using Volume Activation . . . . . . . . . 335
Chapter 12 Deploying with Microsoft Deployment Toolkit . . . . . . . . . 355
Great blogpost by Chaohao Xu regarding PXE Cache Expire in SCCM 2007 SP2
“If a Configuration Manager client has received and started an advertised operating system deployment task sequence, attempting to start another operating system deployment advertisement within a certain period of time might result in the deployment being ignored and failed to start. In this case, the client ignores the PXE boot request and falls back to the local hard disk when booting up.”
Great post fro scug.dk describing how to create a domain join account for use in a OSD Task Sequence.
If you are looking for a simple tool to re-package “Lightweight” Applications and create msi’s, check out: http://www.appdeploy.com/
- Mount Wim file: Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount
- In between step (see walktrough from Microsoft for more detailed information). In my case i updated the hosts file in the image.
- Commit Wim file: Dism /unmount-Wim /MountDir:C:\winpe_x86\mount /Commit
Windows 8 ADK:
If you get this error when trying to import computer information into the SCCM database, it’s probably because a object already exists with the same MAC address. Look for objects imported by various discovery methods. Or if you have enabled unknown computer support, you may have a “unknown computer” object in conflict with the computer object you are trying to import.
A couple of useful paramters for Windows 7, setup.exe. Could be handy when doing scripted installations.
- setup.exe /unattend:\\server\share\unattend.xml
- setup.exe /installfrom:d:\install.wim
In order for client computers to communicate with Configuration Manager 2007 site systems, you must add the following as exceptions to the Windows Firewall:
- TCP Port 80 (mixed mode)
- TCP Port 443 (native mode)
In order to use the remote tools features of Configuration Manager 2007, you need to allow the following ports:
- TCP port 2701
- TCP port 2702
- TCP port 135
Client Push Installation
In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:
- File and Printer Sharing
- Windows Management Instrumentation (WMI)
Great site, describing WMIC aliases: http://ss64.com/nt/wmic.html
A good security practise is to rename the default administrator account. There are many ways to do this. One of them is via WMI:
Example: wmic UserAccount where Name=”Administrator” call rename name=”local_adm”
Having SCCM database hosted on a remote SQL server rather than installing a dedicated instance on a primary site server often have a performance upside.
To succeed with the installation we have some perequsites:
- SQL Server must have registered SPN
- SCCM Admin user (used to run installation) must have sysadmin permissions on the SQL instance
- SCCM Admin user (used to run installation) must be members of builtin/Administrators on the SQL server.
- Computer account of the primary site server should be member of builtin/Administrators
- (If you are installing on a cluster, these perequsites must be applied on both nodes)
If you get this error:
Setup either could not verify that short file name (8.3) support is enabled on the computer specified for site system installation or the server could not be contacted to determine short file name support information. No further prerequisite checking rules can be evaluated on the specified system. Setup cannot continue.
please verify that the user account used to run the sccm perequsite checker have local administrator permissions on the SQL server. Also check that short file name support is not disabled.
Great quick start guide for testing Out of Band Management capabilities with vPro systems in SCCM 2007 SP2.