Thursday, August 16, 2012 5:50 PM
I'm using the syntax below and these settings will not show up after I, update deployment share, regenerate boot images, then add those images to WDS to PXE boot off of them.
Thursday, August 16, 2012 5:53 PMeverything looks fine, what do the logs say ?
David Sebban | Nelite North America | http://www.nelite.com/community/b/dsebban/default.aspx
Thursday, August 16, 2012 5:54 PMNot sure where the logs are? I don't view them for anything.
Thursday, August 16, 2012 6:10 PMI recreated the Deployment Share, and now, it seems to be fine.
Friday, August 17, 2012 7:53 AM
Any time you make any changes to bootstrap.ini you must update your deployment share (which recreates your boot media). If you don't then the only place that your new bootstrap file exists is on the server, and the purpose of bootstrap is to live on your media, be it USB, DVD, CD or PXE.
As for logs, you would really benefit from learning where the logs are as trying to debug a build without logs is never going to be fun.
Look in X:\minint\smsosd\osdlogs, C:\minint\smsosd\osdlogs or C:\Windows\Temp\DeploymentLogs depending on what stage of your deployment you're at.
Friday, August 17, 2012 8:07 AMalso if you use PXE be sure not to forget to replace your boot images on WDS after you updated your deploymentshare
Friday, August 17, 2012 8:16 AM
Go to deployment workbench
Open deployment share
Go to properties and and in rule tab add ur settings in defualt section and check if it works.
Friday, August 17, 2012 11:18 PM
I have seen where changes to the bootstrap.ini does not trigger the boot disks to update. As this post goes, deleting the boot disks and recreating them seem to be the only fix.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked As Answer by TheSuperman76 Saturday, August 18, 2012 8:40 AM
Saturday, August 18, 2012 8:42 AM
Thanks everyone. Just to recap, Yes, I was updating the deploymentshare and completely regenerating the boot images, and yes, I was adding those boot file to WDS.
My deployment share at the time was pretty basic, so I just removed it, and created a whole new one, and that seemed to fix my issue.