SCCM Vista OS depoyment
I am having some issues with deploying operating ysstems using SCCM 2007
I am running under a test enviornement of VM's
I have setup the WDS componentsw needed for PXE boot which point to the configured SCCM boot images
I have imported the workstations to be imaged into "computer association"
I have imported a system image from the sources direcotry of Vista 32bit
I have setup the Operating system install package
I have setup the install task sequence
I have imported the needed drivers
I can get the workstastion to boot and appear to connect to the SCCM. Then after a few minutes the workstation reboots and give an error of "operating system not found"
I have attached some screen shots and log files for review. I have also setup permissions for everyone full control to rule out NFTS or sharing issues.
I have also unchecked "Enable binary differential replication"
I am not sure where to go to resolve this problem.
1.png
2.png
3.png
smsprov.log
component-Status.txt
I am running under a test enviornement of VM's
I have setup the WDS componentsw needed for PXE boot which point to the configured SCCM boot images
I have imported the workstations to be imaged into "computer association"
I have imported a system image from the sources direcotry of Vista 32bit
I have setup the Operating system install package
I have setup the install task sequence
I have imported the needed drivers
I can get the workstastion to boot and appear to connect to the SCCM. Then after a few minutes the workstation reboots and give an error of "operating system not found"
I have attached some screen shots and log files for review. I have also setup permissions for everyone full control to rule out NFTS or sharing issues.
I have also unchecked "Enable binary differential replication"
I am not sure where to go to resolve this problem.
1.png
2.png
3.png
smsprov.log
component-Status.txt
JRoyse
It would be interesting to boot the client with the missing OS with a Knoppix ISO (redirect CDROM device for the client to the ISO file) to see if there is even a file system on the virtual disc.
check "Enable command support" in your boot image properties. When it boots and gets to the system center splash screen hit F8. From the command line look for SMSTS.LOG. This log details whats going on in the task seqence so you can see where it fails. I generally map a drive and copy it somewhere to view with Trace32.
If it is just hanging there before failing I would update everything involved (boot image, driver package, os package, etc..) on the ditribution points.. sometimes it says its there but it still will not work correctly.
If it is just hanging there before failing I would update everything involved (boot image, driver package, os package, etc..) on the ditribution points.. sometimes it says its there but it still will not work correctly.
ASKER
I tried to update everything
Removed the boot images
Removed the install images
Now I get a different error
windows PE cannot start because the actual systemroot directory (z:\windows) is different from the configured one (x:\$Windows.~BT\Windows).
The workstation connects to the PXE server ok and actuall appears to connect to the SCCM server. However right before you see the splash screen from the SCCM I get the above error.
Removed the boot images
Removed the install images
Now I get a different error
windows PE cannot start because the actual systemroot directory (z:\windows) is different from the configured one (x:\$Windows.~BT\Windows).
The workstation connects to the PXE server ok and actuall appears to connect to the SCCM server. However right before you see the splash screen from the SCCM I get the above error.
ASKER
tried to update everything again
Removed the boot images
Removed the install images
Now I get a different error
Now back to the original problem. It's like the OS neever gets sent to the client from SCCM.
Removed the boot images
Removed the install images
Now I get a different error
Now back to the original problem. It's like the OS neever gets sent to the client from SCCM.
Were you able to check out the smsts.log? I think it will be needed to diagnose it further.
ASKER
For some reason the Smsts.log is missing from <CCM Install Dir>\logs
http://technet.microsoft.com/en-us/library/bb932135.aspx
http://technet.microsoft.com/en-us/library/bb932135.aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.