July 2008 - Posts

• PSP Role in SCCM & WDS issues

  Hey ,  I already wrote a previous blog post about this marverlous problem that al the sudden you can't boot anymore from PXE . It says PXE-T01 No boot File found . If you dig deeper into the c:\windows\temp folder there is a  hidden PXEBootfiles folder to see... The problem were goofy ACLs on the c:Windows\temp\pxebootfiles. When I attempted to revised security, I got an Access is Denied message. Once the above directory was deleted, the SMSBoot folder would populate when the bootimage was refreshed on the PXE point. If you get this error, you need to locate the folder (it is hidden), take ownership of it, and delete it. The folder will be at %temp%/PXEBootfiles.  This worked BEFORE SCCM SP1 !!  After I applied SP1 @ customer site , it did not work ... What the hell ?  The solution was simple & logic , but hard to find out why  : If you put an operating system image an select the SMSPXEIMAGES$ Distribution point instead of the normal Distribution point , you will receive an access denied error and the ownership on the %temp%/PXEBootfiles is taken by a goofy SID account that does not resolve. The error occurs because the permissions from the WIM file are applied to the PXE temp folder used for extracting binaries, and the logged in user does not have permissions to delete those folders. Therefore, the PXE service point fails to extract binaries because it cannot delete or access the temp folders for extracting purposes. Make sure that you do not have an OS Image or OS Package being distributed to your \\YOURSERVER\SMSPXEIMAGES$ ! After this step you need to locate the folder (it is hidden), take ownership of it, and delete it. The folder will be at %temp%/PXEBootfiles.Restart the WDS services and the SMSBoot folder would populate automaticaly. PXE boot will work again! Kenny Buntinx Posted Jul 04 2008, 07:08 AM by SCUG.be Filed under: smsv4, SCCM 2007, Configmgr 2007, migration

• How to replace Windows AIK version 1.0 with Windows AIK version 1.1 when you use System Center Configuration Manager 2007

  Microsoft has launched an new article around this . See my previous posts regarding MDT2008  (http://scug.be/blogs/sccm/archive/2008/05/17/installing-osd-deployment-with-mdt-2008-and-get-an-error-in-sms-provider-log-during-mdt-ts-import-custom-boot-image.aspx)  See http://support.microsoft.com/kb/950782/en-us for the full article To replace Windows AIK version 1.0 with Windows AIK version 1.1, follow these steps: 1. Uninstall Windows AIK 1.0 by using the Add or Remove Programs feature in Control Panel, and then restart the operating system. 2. Install the latest version of Windows AIK. For example, use the Waikx86.msi installation file. 3. Export the boot images from Windows AIK. To do this, follow these steps:  a.  Click Start, click Run, type Wbemtest.exe in the Open box, and then click OK.  b.  Click Connect.  c.  In the Namespace field, type root\sms\site_site code, and then click Connect.  d.  Click Execute Method.  e.  In the Object Path field, type SMS_BootImagePackage, and then click OK.  f.  In the Method field, select ExportDefaultBootImage, and then click Edit In Parameters.  g.  Under the Properties field, click to select the Architecture check box, and then click Edit Property.  h.  Next to the Value field, click to select the Not NULL check box, type x86 or x64 under the Value field, and then click Save Property.  i.  Under the Properties field, click to select the ExportImagePath check box, and then click Edit Property.  j.  Next to the Value field, click to select the Not NULL check box, type the path of the image under the Value field, and then click Save Property.         k.  Under the Properties field, click to select the ImageIndex check box, and then click Edit Property.  l.  Next to the Value field, click to select the Not NULL check box, type 1 under the Value field, and then click Save Property.  m.  Click Save Object.  n.  Click Execute. After some time, a dialog box that indicates success appears.   4. In the Configuration Manager console, import the image to System Center Configuration Manager. To do this, follow these steps:    a.  Under System Center Configuration Manager in the Configuration Manager console, expand Computer Management, expand Operating System Deployment, expand Boot Images, and then click Add Boot Image on the Actions pane.  b.  Supply the location and the name of the new boot image that you specified in step 3j for the ExportImagePath value, and then follow the instructions in the wizard to add the boot image.   5. Verify the version of Windows AIK. To do this, follow these steps:    a.  Click Start, point to All Programs, point to Microsoft Windows AIK, and then click Windows System Image Manager.  b.  Click Help, and then click About.The build number for Windows AIK version 1.1 is 6.0.6001.18000.   Kenny Buntinx Posted Jul 03 2008, 03:56 PM by SCUG.be Filed under: smsv4, SCCM 2007, Configmgr 2007, migration

• Importing Drivers in SCCM : Inside view

  Got this one from Brett Flag - OSD team Microsoft  : SCCM defines a driver as an INF file plus its associated content.  When a driver is first imported we do a check to see if the exact same driver (e.g. same INF file and content) has already been imported at the site and prevent it from being imported.  However, if there are any differences then the metadata is read from the INF file (including name, manufacturer, supported operating systems, etc.) and a new driver object is created. It is not uncommon for hardware vendors to package different INF files for each operating system they support in the same directory.  When this happens, SCCM will create a driver object for each INF file but it is smart enough to only keep a single copy of the content.  Since the default name of a driver comes from the supported hardware list in the INF file, each of these driver objects will likely get the same default name even though they support different operating systems (to see if this is the case, check out “Applicability” tab on the Driver’s preview pane). There are a few things you can do about this: SCCM generates a default name for a driver based on the hardware that it supports – but you can change this in the driver’s properties screen. Add additional columns to the Drivers view so that you can tell the difference between the drivers: Select the Drivers node in the Admin UI Run the View - Add/Remove columns… action Select additional columns to display (for example “INF File”) Ignore it – Since SCCM automatically determines driver applicability at deployment time you don’t really need to worry about the specific drivers in the driver catalog. After importing a driver you can review the driver catalog matching reports (“Driver catalog matching report for a specific computer” and “Driver catalog matching report for a specific collection”) which use hardware inventory information to predict what drivers match devices in your environment to give you a better idea of how the drivers will be used.  Thanks Brett ... Regards,  Kenny Buntinx Posted Jul 02 2008, 02:57 PM by SCUG.be Filed under: smsv4, SCCM 2007, sms v4, configmgr2007, sccm2007, Configmgr 2007, migration

• Update : OSD deployment with XP SP3

  Today I used my new OSD deployment package in SCCM with XP SP3 and when I wanted to "Prepare my OS" the task sequence always failed with errorcode 0x08000002.I was figuring out what the hell was going on and then I found it . For XP SP3 you will need the updated "Deploy.cab" with sysprep. There have been changes to sysprep in XP SP3. I have updated my pages to reflect this but the issue deals with the default profile and it no longer being copied when running sysprep. Before SP3 and without the patch the default profile was copied from the administrator account during the sysprep process, this behavior however changed in SP3 or when you installed the hotfix 887816. In SP3 the default setting is to not copy the default profile, thus a new key was added to sysprep.inf to allow for this functionality. The UpdateServerProfileDirectory=1 setting tells SP3 to copy the administrator profile to the default profile during the sysprep process.  Hope it works out for you ,  Kenny Buntinx Posted Jul 02 2008, 02:47 PM by SCUG.be Filed under: smsv4, SCCM 2007, sms v4, configmgr2007, sccm2007, Configmgr 2007

• Exchange Server 2007 Management Pack Update!

  A while ago I posted about the management pack Roadmap and the fact that we where stille waiting for an update of the Exchange 2007 Mp. Now here it is! Overview The Microsoft Exchange Server 2007 management pack is designed to be used for monitoring Exchange 2007 events, collecting Exchange component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically responding to critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage Exchange servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, health monitoring, and centralized management. This Management Pack requires Operations Manager 2007 Service Pack 1. This Management Pack requires the Operations Manager 2007 updates specified in Knowledge Base articles 950853, 951979 and 951380 (see the Management Pack Guide for details). Release History: 10/9/2007 - Initial Release, version 6.0.5000.0 6/22/2008 - Updated Release, version 6.0.6278.12     You will need some hotfixes: KB 950853 951979 951380 Greetz, Alkin  Posted Jul 02 2008, 02:27 PM by SCUG.be Filed under: Operations Manager 2007, Management Pack

• System Center Mobile Device Manager 2008 Management Pack

  Overview Microsoft System Center Mobile Device Manager 2008 Management Pack for Operations Manager 2007 provides proactive monitoring of your Microsoft System Center Mobile Device Manager 2008 environment. This management pack includes: Detection and monitoring of all MDM servers and dependent services The alert-driven state Performance and backlog monitoring and configuration Before you install the MDM management pack, read the MDM Management Pack Guide document. The guide includes instructions that you need to correctly deploy, configure and use the management pack. Feature Bullet Summary: The System Center Mobile Device Manager (MDM) 2008 Management Pack for Operations Manager 2007 provides capabilities for MDM 2008 monitoring, including the following: Collection of events from MDM Device Management Server, MDM Enrollment Server, MDM Gateway Server, and MDM Self Service Portal. Health state monitoring and alerting for MDM service errors requiring administrative intervention. Collection of MDM performance counters from MDM Device Management Server, MDM Enrollment Server, MDM Gateway Server, and MDM Self Service Portal. Events indicating service outages Alerts indicating configuration issues and connected data source changes Verification that all dependant services are running Management Pack Release History: 6/30/2008 - Version 1.0.2300.0 Original release of the English version of the Management Pack Download the Management pack Here Posted Jul 02 2008, 01:45 PM by SCUG.be Filed under: Operations Manager 2007, Management Pack

• Deploying a Windows XP SP3 "Gold image" with SCCM 2007

  This post and subsequent posts will be a step by step on how to build a base XP SP3 image in SCCM. I will be outlining not necessarily pointing out every click. Hopefully others will find this helpful. This assumes an understanding of SCCM and uses what is refereed to as a “Thin Image Strategy”. Create a network access account, it only need be a domain user and its password should not expire. Add the account to the Computer Client Agent in the Client node under Site Settings Import XP SP3 as an operating system Install Package. Add a Distribution point to your new XP SP3 package created in step 1 Create the XP SP3 sysprep package in SCCM The Deploy.cab included on the CD was not updated properly for XP SP3 so you must download a new version here. Create a package that points at the extracted CAB file for its source You do not need to create any programs for the package the build task sequence takes care of this Add the package to a DP that can be used during your build Create a package for the Config Mgr Client Specify always obtain file from source directory Usually here I create a share at \\SCCMSERVER\Souce$\SCCMClient. Update the ccmsetup command line properties accordingly. Extensive information about command line properties on TechNet here. Add the package to a DP that can be used during your build Create a “Build and capture a reference operating system image” task sequence Name the task sequence something appropriate like “Build & Capture Windows XP SP3 Gold Image” Select the x86 boot image Select the Operating System Package you created in step 1 Enter a product key Set the local admin password to any password Join a workgroup Select the Config Mgr client you created in step 4 Don’t add any software to the base image Set your image properties Select a location to save the image and make sure you include the full path including the .wim extension Enter an account with rights to write to the share Finish up Change the task sequence to use “Quick Format” Right Click on the Task Sequence and choose Edit Select the “Partition Disk 0″ step Choose properties on the Default (Primary) partition and check the “Quick Format” option Create a collection to which you will advertise the task sequence; I usually use  "customer" Base Builds Advertise the task sequence to the collection you created in step 7 as optional Right click Task sequence and choose advertise, follow the wizard Make sure you select the check box “Make this task sequence available to boot media and PXE” If you are in test and your boundaries are not defined make sure you select “When no local distribution points are available, use remote distribution point” Make sure you completed step 1 Ensure that you have the network and mass storage drivers to boot the device on the boot image and in the driver store (If you have to do this in the future you must update the PXE and standard DPs) Add the appropriate boot images (x86 / x64) to the PXE and standard DPs Allow the client to boot from PXE If this client previously had an SCCM agent on it you just need to add the client to the collection you created in step 6 If this is a new client and SCCM is pre-R2 add the client manually Add the client by right clicking the Computer Associations node under OSD and choosing “Import Computer Information” Enter the Name of the computer Enter the MAC and or SMBIOS GUID Add the computer to the collection you created in step 7 Boot the device up to PXE and choose your task sequence. In less than an hour you should have the start of a great XP Image Kenny Buntinx Posted Jul 01 2008, 03:23 PM by SCUG.be Filed under: smsv4, SCCM 2007, sms v4, configmgr2007, sccm2007, Configmgr 2007, script