OSDisk appears as D:
This has been driving me totally crazy for a while! Finally I found the solution, which is always simple when you know it.I've been trying to deploy the original install.wim from the Windows 7 media with SCCM 2012, and every time, OSDisk appeared as D:.First of all, you should select "Apply operating system from an original installation source" in the "Apply Operating System Image" task. You should also have the "Set Variable for Drive Letter" set to False. Both settings are found in the Install section.The last and final setting, that took me a while to find, was in the Preinstall section and the task "Format and Partition Disk 6.1". For some reason, Microsoft has left the "Do not assign a drive letter to this partition" unticked for the BitLocker BDEDrive.I hope this helps someone out there...Cheers!
Configuration Manager Remote Control Disabled after install
After installing the Configuration Manager client on a Windows XP workstation. The client appears to install fine but the Configuration Manager Remote control service is stopped and the startup type is set to disabled. My ccmsetup.log says the install was successful and the client shows up in the configuration manager console.
To solve this issue, start by changing the following values in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control
Access Level 0 => 2
Allow Local Administrators to do Remote Control 0 => 1
Audible Signal 1 => 0
Enabled 0 => 1
Firewall Exception Profiles 0 => 15
Permission Required 1 => 0
PermittedViewers Administrators => blank
Finally, set the service Configuration Manager Remote Control to Automatic and start it.
I do not know why this happened, but I'm suspecting that it has something to do with the client not being assigned to a boundary group.
Failed to get client identity (80004005)
PXE keeps rebooting after Preparing network connections.
Errors in smsts.log:
reply has no message header marker
Failed to get client identity (80004005)
failed to request for client
Resolution: Set correct time and date in BIOS
Source: http://msitpros.com/?p=58
SCCM Agent not working after OS deploy
The agent doesn't get the self signed certificate after os deployment.
Right after the "Setup Windows and ConfigMgr" step, add two "Run Command Lines" to set the registry values correctly. Here are the two commands to be run:
REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f
REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f
Please read more here: http://www.windows-noob.com/forums/index.php?/topic/5618-damaged-client-after-setup-no-self-singed-cert/
Windows XP bluescreens after OS deployment
Don't forget to include mass storage driver. You can get a driver pack that covers the most models on the link below.
Create a Driver Package including all the drivers from the link above, then create a Apply Driver Package step in your Windows XP task sequence selecting the newly created Driver Package.
SCCM 2012 Windows XP OSD installing to D:
I've been having issues with Windows XP being deployed to D:, and finally I've found the solution.
There's an error in the MDT task sequence step "Format and Partition Disk 5.x".
In the Options tab there's some conditions, and one condition is:
ImageOSVer equals 5.1 AND ImageOSVer equals 5.2. I will now tell you - THIS WILL NEVER HAPPEN ;)
Change this by adding an If-statement matching ANY of the listed conditions.
Now, the disk will get partitioned and formatted and the OS will end up at C:.
Out!
Deployment not working on new Distribution Point
Been having trouble getting PXE deployment working on a new DP.
Looking in C:\SMS_DP$\sms\logs\SMSPXE.log I found:
Warning: Matching Processor Architecture Boot Image (0) not found
The solution is to make sure you to have both x64 and x86 images deployed even if you aren’t going to use both of them.
For both of your boot images, ensure ’Deploy this boot image from the PXE service point’ is ticked and then make sure you ‘Distribute Content’ to your PXE enabled DPs.
