ssx4life

Also, I'm going to start doing a full walkthough on FOG from start to finish when it comes to imaging a pc. Check the fog documentation and website for more info.

Wow lots of things here, lets break it down shall we? #1 glad you are interested in computer imaging. There are LOTS of different ways to image a pc and set up a computer for a work envyroment. You are going to want to start by reading though MSFN's unattended xp installation guide - MSFN's Unattended Windows : Unattended Windows Introduction You put [fog] in the title of the post so i'm assuming you are using FOG to image pc's correct? You also are going to want to sysprep your computer images. I'm assuming you have a VLK for Windows XP and aren't using OEM for everything. #2 you need to be a bit more specific about the lab setting. If you don't all of the same hardware this makes your life alot harder. By harder I mean ALOT harder. How many different hardware models do you have? 10 or more? 15 or more? You are going about this the wrong way. You are going to want to end up sysprep'ing the pc's that are not on the domain (do a mini-setup + reseal). Fog has lots of extra features that will make your life easier (auto changing computer names + adding it to domains) Lots of stuff to go over here, so take it one step at a time. If you need help with creating an image let me know (hardware independent imaging is no easy task)

never mind, fixed it. oh btw you don't need to use external .vbs scripts to change host names and or add system's to AD. =) FOG service does it all

First of all thank you whitenight639 for your information on the scripts. Could you please be a bit more detailed on a few pointers for me here? I'm trying to replicate what you have done with FOG when it comes to renaming the clients based off of serial # + rebooting. I'm attempting to do all of this via sysprep.inf ;SetupMgrTag [unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 TargetPath=\WINDOWS [GuiUnattended] AdminPassword="*******************" EncryptedAdminPassword=YES TimeZone=20 OemSkipWelcome=1 OEMSkipRegional=1 AutoLogon=Yes AutoLogonCount=1 [userData] ProductKey=WDWCD-QBBPF-*****-*****-***** FullName="XXXXXXXXXX" OrgName="XXXXXXXXXX" ComputerName=* [TapiLocation] AreaCode=XXX [identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes [branding] BrandIEUsingUnattended=Yes [Proxy] Proxy_Enable=0 Use_Same_Proxy=0 [GuiRunOnce] Command0="cscript.exe %systemdrive%\system32\compname.vbs" I have tested your .vbs standalone and it works as intended on our hardware. Now I'm looking to implement it into our fog images, and I'm hoping you can point me in the right direction. 1. System is sysprep'ed and auto logs in after the final restart. 2. I see a dos window appear during the inital login, which tells me that the script is indeed running. However I do not get a window confirming the change. Could you please tell me how you get your commands to run? Do you run a .bat script in which a .vbs is contained? I'm adding the systems to AD via FOG which is working great. Any help would be appreciated. Thanks, --ssx--

Ok here we go post #2. I was cruising though the web looking for a .vbs for fog and ran into this fourm. Decided to register just to answer your questions! =) FOG documentation has been growing, so please see the full documentation on how to add different applications into the PXE boot menu - Am I able to modify the PXE menu to run other applications? - FOGWiki Thanks, and if you need more help let me know --ssx-- p.s any DOS based application can be run under FOG with the proper parameters.

I have an answer for you, but I just registered. Your site doesn't let me post links on the 1st post.