Windows 7 Deployment FOG- SAD2 Driver tool
-
This guide is amazing, no doubt. But I’ve got a question about where
[CODE]shutdown -r -c “Drivers Installed! Machine will now restart…”
START C:\Drivers\SAD2-111118\RemoveD.cmd
EXIT[/CODE]is or goes. I can’t find it in any of the configuration files already provided or where to put that.
Thanks so much for this awesome guide, it’s really helped me out a ton!
-Alex
-
hi all weve just started rolling windows 7 out and thought id ask a few things, the sysprep scenario is a right faff from reading the great articles here it makes more sense but to clarify, should i be editing machines in audit mode first then sealing up with a full sysprep/ generalize? ON a test machine in a lab im getting a odd error when i go to log in on domain it keeps saying No windows logon servers to service this request any body seen this isse before? its a mixed domain between 2003/2008 domain controllers
-
[quote=“nb27alex, post: 2265, member: 162”]This guide is amazing, no doubt. But I’ve got a question about where
[CODE]shutdown -r -c “Drivers Installed! Machine will now restart…”
START C:\Drivers\SAD2-111118\RemoveD.cmd
EXIT[/CODE]is or goes. I can’t find it in any of the configuration files already provided or where to put that.
Thanks so much for this awesome guide, it’s really helped me out a ton!
-Alex[/quote]
Hi Alex,
I can’t upload the .cmd file here, so just copy and paste the below into a text file, and renmae the file “RemoveD.cmd” then you need to place it in the directory where the DPinstall tool calls it to run, which is:
C:\Drivers\SAD2-111118\
All it does is just delete the Folder C:\D which is created during the driver pack tool running, and it delete the driver packs from the C drive. You don’t really need it but it just helps clean up a little.
This is the script:
@ECHO OFF
rd /s/q C:\D
DEL /F /S /Q /A “C:\Drivers\SAD2-111118”
rd /s/q C:\Drivers\SAD2-111118
EXIT
-
[quote=“pallytank09, post: 2258, member: 731”]I really like this process and I am working on implementing it right now at my company. I do have a couple of questions though.
1.) The SAD2 program that I am using is rather old. The links in the thread you reference to the software download fail. I had to dig back quite a few versions to find one that could be downloaded. Any chance you can post the most recent version you have here or email it to me?
2.) When using your guide, the setupcomplete.cmd script runs on the initial login and calls SAD2 to run. When my syspreped install finishes it does run the script and call SAD2 but SAD2 doesn’t get anywhere other then trying to start because windows is still in the process of coming up and logging in. It seems like the setupcomplete script runs to soon.
Any thoughts?[/quote]
Hi, the DPinstall tool is basically just a .cmd script. It’s attached as a .txt to the first or second post. But I’ve made one small change, which is that I added “NET STOP “Fog Service”” to the start, and end of the script to avoid fog restarting while the tool is running. I will attach the updated script that I use, as a .txt file. You will need to rename it .cmd extension, and then replace the “DPInstallTool.cmd” in the SAD21111118 folder. You can download the version I use here:
[url]http://www.mediafire.com/file/aea3yle91uh3lrl/SAD2-111118.7z[/url]
Or you can check the latest releases here:
[url]http://forum.driverpacks.net/viewtopic.php?id=5336[/url]
I think the guy who wrote it occasionally releases newer versions of the script, but for my purposes this works, and believe me it has been tested thoroughly.
As to the tool starting while windows is starting up, yes, the setupcomplete.cmd script will run, and it doesn’t seem to obey “SLEEP.exe” from what I’ve tested. This is how it works for me, but as long as you configure your unattend.xml file to automatically log on as administrator one or two times after install, then the DPinstall tool starts, then windows logs on as admin, and the dp install tool runs no problems.
If you want to get the script to be a little delayed, then since it ignored “SLEEP.exe” you might be able to add something like this to the start of the script:
[FONT=Verdana][COLOR=#000080][COLOR=#000000]For any MS-DOS or Windows version with a TCP/IP client, [COLOR=#005900]PING[/COLOR] can be used to delay execution for a number of seconds.[/COLOR]
[COLOR=#000000]If specified (-w switch), [COLOR=#005900]PING[/COLOR] will wait for a number of milliseconds between two pings before giving a time-out.[/COLOR][/COLOR][/FONT]
[COLOR=#005900][FONT=Courier New][COLOR=#000000]PING 1.1.1.1 -n 1 -w 60000 >NUL[/COLOR][/FONT][/COLOR]
[COLOR=#005900][FONT=Courier New] [/FONT][/COLOR]
[COLOR=#005900][FONT=Courier New][COLOR=#000000]I haven’t tested if this works though with the setupcomplete.cmd.[/COLOR][/FONT][/COLOR] -
[quote=“Darren George, post: 2272, member: 375”]hi all weve just started rolling windows 7 out and thought id ask a few things, the sysprep scenario is a right faff from reading the great articles here it makes more sense but to clarify, should i be editing machines in audit mode first then sealing up with a full sysprep/ generalize? ON a test machine in a lab im getting a odd error when i go to log in on domain it keeps saying No windows logon servers to service this request any body seen this isse before? its a mixed domain between 2003/2008 domain controllers[/quote]
Hi,
Yes you should make all changes to the PC while it is in audit mode, as per the instructions. I haven’t had that problem myself with win 7, it might be best to start a new thread in windows related.
-
Hello All,
this is my first attempt with FOG. I’d heard about it in the past, but until this tutorial came along, I wasn’t sure if creating a hardware-independent image was possible. We currently use Altiris, which allows us to have a hardware-independent image. However, we are not interested in upgrading to the latest version of Altiris so we are exploring some options. Basically, I set up fog in about 30 minutes, and I spent the better part of this afternoon creating a “master” vm machine to take the image from. Not being familiar with this process, when I reached step 9 and got to this point
“And install the FOG client service. [BE SURE TO REPLACE YOUR “Hostnamechanger.dll” or your machine won’t rename and add to domain after imaging”. Replace this after FOG client is installed."I wasn’t sure how to proceed. I installed the client service but did not reboot. I then went and found hostnamechange.dll and deleted it. I don’t think that was the proper procedure, but I’m unclear.
Any advice appreciated.
Thanks,
Brad -
[quote=“brad johnson, post: 2363, member: 733”]Hello All,
this is my first attempt with FOG. I’d heard about it in the past, but until this tutorial came along, I wasn’t sure if creating a hardware-independent image was possible. We currently use Altiris, which allows us to have a hardware-independent image. However, we are not interested in upgrading to the latest version of Altiris so we are exploring some options. Basically, I set up fog in about 30 minutes, and I spent the better part of this afternoon creating a “master” vm machine to take the image from. Not being familiar with this process, when I reached step 9 and got to this point
“And install the FOG client service. [BE SURE TO REPLACE YOUR “Hostnamechanger.dll” or your machine won’t rename and add to domain after imaging”. Replace this after FOG client is installed."I wasn’t sure how to proceed. I installed the client service but did not reboot. I then went and found hostnamechange.dll and deleted it. I don’t think that was the proper procedure, but I’m unclear.
Any advice appreciated.
Thanks,
Brad[/quote]Hi, you need to edit your own “hostnamechanger.dll” so that your machines can join to the domain etc. You don’t want to delete it entirely. It should rename machines for you even if you don’t change it. But it won’t add your machines to active directory in it’s standard form.
[url]http://www.fogproject.org/wiki/index.php?title=Managing_FOG#Hostname_Changer[/url]
-
[quote=“andyroo54, post: 2364, member: 267”]Hi, you need to edit your own “hostnamechanger.dll” so that your machines can join to the domain etc. You don’t want to delete it entirely. It should rename machines for you even if you don’t change it. But it won’t add your machines to active directory in it’s standard form.
[url]http://www.fogproject.org/wiki/index.php?title=Managing_FOG#Hostname_Changer[/url][/quote]
I have never edited hostnamechanget.dll. I just install fog service before sysprepping and add AD credentials to FOG web ui.
My machines rename on deploy and join the domain just fine -
[quote=“falko, post: 2367, member: 48”]I have never edited hostnamechanget.dll. I just install fog service before sysprepping and add AD credentials to FOG web ui.
My machines rename on deploy and join the domain just fine[/quote]Yeah I’, not really sure but I couldn’t get mine to work even with credentials in FOG web ui, our FOG server was setup by the person before me, I’ve only ever set one up at home just to try it out for myself on an old PC. But I found unless I used the Hostnamechanger.dll from his original XP image it wouldn’t join to the domain. So I assumed he must have edited it with credentials or something…
-
Google helps here
[url]http://www.edugeek.net/forums/o-s-deployment/37654-fog-active-directory.html[/url]
Also look @ page 27 of this guide - [url]http://wiki.rscwmsystems.org.uk/images/4/47/Using_Fog.pdf[/url] -
Nice Guide!
It is possible to use netdom to join domain in win7 also, so any other good reason to install the fog service, than the join domain functionality? To use netdom you have to install the windows 7 admin tool, but it is pretty simple to install. -
Fog service also pushes out software packages you can customize and build yourself. Can auto-shut down / log off / modify clients remotely (big help).
If you don’t want to use Active Directory for all your software pushing and updates it’s a great work-around solution.
-
[quote=“ssx4life, post: 2401, member: 268”]Fog service also pushes out software packages you can customize and build yourself. Can auto-shut down / log off / modify clients remotely (big help).
If you don’t want to use Active Directory for all your software pushing and updates it’s a great work-around solution.[/quote]
As SSX says, For me one of the best features of FOG is to deploy programs automatically. It’s one thing to save two hours installing windows 7, but it’s another game all together installing programs automatically after imagine. Saves time like you wouldn’t believe.
-
is it possible to attach the latest cmd/text file that you use, i dont want to have missed anything out?
thanks
-
This post is deleted! -
Awesome guide. Trying to test this right now. Thanks OP!
-
Nice feature In other words, how does the actual deploy method work?
Policy ? or does the package dploy with pxe boot?
I am whery curious about the agent, and the resources it uses on our clients.
The main reason that i have not considered the agent is that we have bad experience with this sort of agents, we where running Novel Zenworks before fog, and the agent from novel kille about 50% of our computers esepessially those with 1 gb ram or less. -
[quote=“falko, post: 2464, member: 48”]is it possible to attach the latest cmd/text file that you use, i dont want to have missed anything out?
thanks[/quote]
Here you go, I haven’t changed much, (Just to Stop/start FOG service, and clean a few things up) you can compare the differences yourself (if you use it, just remember to change it back to a .cmd file, it won’t let me upload .cmd files):
[url=“/_imported_xf_attachments/0/85_DP_Install_Tool.txt?:”]DP_Install_Tool.txt[/url]
-
thank you, your guide is truly awesome!!
-
Andyroo54 would you be kind enough to go back to the original post in the thread and add the DP_Install_Tool.txt to the first entry? This will keep the thread uniform and simple to manage.
Also… if you could please upload an example of your .xml answer file for the community. Just a thought
p.s. i’m working on a tutorial for XP as well for all those legacy users holding out
–ssx–
