You may be having trouble deploying an operating system to a brand new machine even after you have advertised an OS deployment task sequence to it’s correct MAC address. You might be receiving any one of the following errors: PXE Boot aborted. Booting to next device MAC=70:71:BC:88:C3:BC SMBIOS GUID=00000011-4918-8015-BF5A-888888888788 > Device found in the database. MacCount=1 GuidCount=1 The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned The SMS PXE Service Point instructed device to boot normally since it has no PXE advertisement assigned Generally on any machine the MAC address and the…

To grant access to remotely open the Configuration Manager 2007 R3 console requires the following steps: Ensure the user is a member of the SMS admins group on the SCCM server Use the DCOM tool to add remote launch permissions to that group – straight out of the help file: To grant Remote Activation permissions to the SMS Admins group From the Start menu, click Run and type Dcomcnfg.exe. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties. In the My Computer Properties dialog box, on the…

Client installation log file located on the client: %windir%\system32\ccmsetup\ccmsetup.log …or %windir%\ccmsetup\ccmsetup.log Installing the SCCM client manually is a simple case of running a command directly from the SCCM site share. \\servername\SMS_<sitecode>\Client\ccmsetup.exe A number of command line options are available if the Active Directory Schema hasn’t been extended for Configuration Manager 2007, these options are not needed if AD has been extended and Publish this site in Active Directory Domain Services is selected in the Advanced tab of the Site Properties dialog box, then client computers will automatically search Active Directory for installation properties. /mp:SMSMP01 – Specifies the management point SMSMP01…

One of the fundamental things you need to do with any SCCM installation and deployment, you need to get the basics right. Queries are those basic building blocks which everything else in SCCM is based on. Once you have all your custom queries setup, then you can setup collections based on the queries, once this is done, all other SCCM components is relatively strait forward. A good way to target separate machines in queries and collections is by their Chassis Type. Chassis Types 1 Other 2 Unknown 3 Desktop (Virtual machines as well) 4 Low Profile Desktop 5 Pizza Box…

msiexec /Option <Required Parameter> [Optional Parameter] Install Options </package | /i> <Product.msi> – Installs or configures a product /a <Product.msi> – Administrative install – Installs a product on the network /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>] – Advertises a product – m to all users, u to current user </uninstall | /x> <Product.msi | ProductCode> – Uninstalls the product Display Options /quiet – Quiet mode, no user interaction /passive – Unattended mode – progress bar only /q[n|b|r|f] – Sets user interface level         n – No UI         b – Basic UI         r – Reduced UI        …

In the registry, add the following DWORD key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents Set the value to decimal 255 – then reboot.

By default this is very annoying, as the window keeps popping up as soon as the cursor hovers over the top, here is how you can customise the hover time just for the taskbar: Click on the Start Button and type in Regedit and hit Enter. Navigate through HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced. Right click on Advanced and select New DWORD and name the new value "ExtendedUIHoverTime". Right click on ExtendedUIHoverTime and select Modify. Switch to Decimal base and enter in your new number.  The default is 400 milliseconds. So set it to something like 9000, which is 9 seconds delay, up to you….

Troubleshooting SCCM 2007 R3 is pretty complex, log files are your friends. IIS log files are used a lot in Native Mode setups – C:\inetpub\logs\LogFiles\W3SVC1 Server Log Files – %ProgramFiles(x86)%\Microsoft Configuration Manager\Logs ConfigMgr distribution point ConfigMgr management point (MPSetup.log) ConfigMgr reporting point (rsetup.log & SMSReportingInstall.log) ConfigMgr software update point (SUPSetup.log) onfigMgr server locator point (SMSSLPSetup.log) ConfigMgr fallback status point (SMSFSPSetup.log) ConfigMgr Reporting Services Point (SRSRPSetup.log) ConfigMgr state migration point (SMSSMPSetup.log) Ccm.log – Records client configuration manager tasks Fspmgr.log – Records fallback status point activities Hman.log – Records site configuration changes, and publishes site information in Active Directory Domain Services Mpcontrol.log…