Navigate to Deploy > Deployment Points > Right Click on the OSD Deployment Point and select PROPERTIES.
Click the RULES Tab and modify the rules as shown below. be sure and use the actual name of your SMS Server and Database.
[Settings]
Priority=Default
[Default]
OSInstall=Y
ScanStateArgs=/v:5 /o /c
LoadStateArgs=/v:5 /c /lac
UserDataLocation=AUTO
[SMS]
SQLServer=NAME OF YOUR SMS SERVER
Database=NAME OF YOUR SMS DATABASE
Table=v_Program
Parameters=PackageID, Programname
SQLSHARE=SMSClient
- At this point in Johans Guide he calls for editing the bootstrap.ini file. However we do not have our image package yet and therefore do not know the PkgID nor the Program name. We will return to this in a little bit.
Select the Builds Tab. Notice the Red Exclamation point on the right hand side. It indicates that a Non OSD image is selected for the OSD Deployment type.
Ensure only your OSD Captured Image is selected.
Click the WindowsPE 2004/2005 Tab and select Windows PE 2005 for Windows PE Source and Windows 2003 SP1 OS for Windows Source then click OK
Right Click on your OSD Deployment Point and Select UPDATE.
I had a few issues trying to do this. First I recevied an error about MSXML3 files not being in the OSD Directory so I went and downloaded them from
http://www.microsoft.com/downloads/details.aspx?FamilyID=b997d23c-cbe3-44d3-8798-2feb1df815c3&DisplayLang=en.
Then I extracted all of the files.
Then I copied them to \SMS\OSD on the SMS Server and realized they were already there!
That was not the issue. When I selected to make the ZTI share I tried to make it on another machine - not the machine with my Deployment workbench on it.
And what I found was that even though the Wizard told me the OSD Deployment point was successfully created it really is not created (at least the ZTI$ share is not) until you try to update the files
When I tried to update the files I received the MSXML file error.
So I deleted the OSD Deployment point and recreated it on the same machine as my Workbench. Then I was able to update it without error.
I would think it should handle putting the ZTI share on another machine, especially since the wizard checks the remote machine.
I will try to figure this out later. For now I just want to keep going and get it functional.
NEXT - Update Windows PE 2005 In SMS