fly

Its great. I have my gripes, but overall its an excellent product. In fact, I'll ask here about my main one. Maybe you guys will know... Our Outlook domain is different from our corp domain. USMT assumes they are the same, therefore I have to change every users Outlook login (or help them do it) to read: enterprise\id instead of tcs_main_dom\id

Hmmm... Yeah, I'd be interested in that script for sure!

BTW, thanks for your help. Im going to try this out today.

Wow. Gee, ya think they could put that in their documentation?

It's my understanding that network connectivity isn't "guarenteed" during GUIRunOnce. I think I read that at M$ anyway...

You're using /all. That overrides /ui:90 as far as I can tell...

Yep. Using a domain admin account.

I can't seem to get the USMT switch /ui:90 to work. It is supposed to only grab accounts that have been active in the last 90 days, but it only seems to grab the account I am logged on with. I assume this is a huge bug. Can anyone confirm this?

You helped me a couple of weeks ago over ICQ. And your process sounds interesting. When compared to RIS, is it easier or harder to learn?

Can you explain what the advantages to that are over RIS? edit: btw, do you have paypal? I wanted to pay you for helping me.

Sweet. I'll have to get the company to pick this one up for me.

Very interesting. Here is what I ended up doing... This script is called by GUIRunOnce Option Explicit ' Set variables Dim oShell, oFSO Dim sOutputFile, aBiosString, iBiosRecords, sCurBiosString, sAPIC Dim sUniArray, sMultiArray, sModel ' Setup arrays ' sUniArray is for Dell models with a Uniprocessor ' sMultiArray is for Dell models with a Multiprocessor (Hyperthreading included) sUniArray = array("GX260") sMultiArray = array("GX270", "GX280") '**Start Encode** ' The line above exists if there is a desire to encode the script for security reasons. ' To encode the script, download the script encoder via the link below. ' http://www.msdn.microsoft.com/library/default.asp?url=/downloads/list/webdev.asp Set oShell = WScript.CreateObject("WScript.Shell") Set oFSO = CreateObject("Scripting.FileSystemObject") ' Set our APIC value to initially be false sAPIC = False ' Run SMBios to find settings sOutputFile = oShell.ExpandEnvironmentStrings("%TEMP%") & "\Bios.TXT" oShell.Run "CMD.Exe /C c:\tcs\sysprep\SMBiosD.Exe > " & sOutputFile,0,True ' Read temp file into an Array aBiosString = Split(UCase(oFSO.OpenTextFile(sOutputFile,1,False).ReadAll),vbCrlf) iBiosRecords = CStr(UBound(aBiosString)+1) ' Delete temp file oFSO.DeleteFile sOutputFile ' Find the exception we're looking for (Uniprocessor) For Each sModel in sUniArray For Each sCurBiosString in aBiosString If Instr(1,Ucase(sCurBiosString),sModel,vbBinaryCompare) <> 0 Then sAPIC = "Uni" Exit For End If Next Next ' Find the exception we're looking for (Multiprocessor) For Each sModel in sMultiArray For Each sCurBiosString in aBiosString If Instr(1,Ucase(sCurBiosString),sModel,vbBinaryCompare) <> 0 Then sAPIC = "Multi" Exit For End If Next Next ' Do stuff with results If sAPIC = "Uni" Then oShell.Run "C:\tcs\sysprep\DevCon sethwid @ROOT\ACPI_HAL\0000 := +acpiapic_up !acpiapic_mp",1, True oShell.Run "C:\tcs\sysprep\DevCon update c:\windows\inf\hal.inf acpiapic_up",1, True ElseIf sAPIC = "Multi" Then oShell.Run "C:\tcs\sysprep\DevCon sethwid @ROOT\ACPI_HAL\0000 := +acpiapic_mp !acpiapic_up",1, True oShell.Run "C:\tcs\sysprep\DevCon update c:\windows\inf\hal.inf acpiapic_mp",1, True End If wscript.quit I barely know how to script anything, so the code probably looks horrible. But thanks to this thread, I now have only ONE image to maintain for all my PCs.

Thanks again for your input guys.

This should be possible with ta.exe that's included as a dos command tool with windows xp embedded. When you run it, it will create a report file (devices.pmq) with the HAL-type that SHOULD actually be installed (which is not necessarily the one that IS installed) Here's a code snippet that should be run (instead of setup.exe) at first boot of the deployed pc. As you may understand that reg setting was saved (sysprep.reg) and changed just after "sysprep -mini -quiet -reseal -noreboot" and before you shut the master-pc down. O, I forgot; Your HAL should be set to "Standard HAL" on the master-pc beforehand. -This should pretty much work on ANY pc/laptop that can run XP -Remember: This is NOT supported by M$. <{POST_SNAPBACK}> I'm not sure I follow what you're doing there. Can you explain further? edit: Let me elaborate. What is in the sysprep.reg file? And where to I get ta.exe?

Now I need to be able to figure out if hyperthreading is enabled, and I can use 1 image for all PCs...

I think I fixed it, but I don't know how/why... Dim oShell, oFSO Dim oOutputFile, aBiosString, iBiosRecords, sCurBiosString, sAPIC Set oShell = WScript.CreateObject("WScript.Shell") Set oFSO = CreateObject("Scripting.FileSystemObject") ' Set our APIC value to initially be false sAPIC = False sOutputFile = oShell.ExpandEnvironmentStrings("%TEMP%") & "\Bios.TXT" oShell.Run "CMD.Exe /C c:\SMBiosD.Exe > " & sOutputFile,0,True 'Read temp file into an Array aBiosString = Split(UCase(oFSO.OpenTextFile(sOutputFile,1,False).ReadAll),vbCrlf) iBiosRecords = CStr(UBound(aBiosString)+1) 'Delete temp file oFSO.DeleteFile sOutputFile 'Find the exception we're looking for For Each sCurBiosString in aBiosString If Instr(1,Ucase(sCurBiosString),"ON-CHIP APIC SUPPORTED",vbBinaryCompare) <> 0 Then sAPIC = True wscript.echo "True" Exit For End If Next When I took the () off the variable aBiosString, it worked. I thought that signified that it was an array, and it looks like an array in the code, so hopefully someone can say why that fixed it and/or if it really did...

Okay, I separted out the line and the error seems to be in the Split command. Or so my lack of VB knowledge tells me...

Script hacker, yep thats me. Anyone?

bump. Did anyone try this? I got it to create the file, but the app appears to hang after that. I'd love to use this to just have one image...

Well, I guess that settles it. I should be using RIS...

I'm guessing this topic has been brought up many times, but I was unable to find it in my brief searches. Thanks for any input... So, what do YOU find to be the best option for deploying new PCs? I'm currently using sysprep + ghost to roll out new PCs, but am looking for a better option. I don't mind doing a lot of homework upfront to make it easier in the end. Is RIS worth the time? Should I try this? Some sort of unattended install? Am I doing it the best way? Again, thanks for your input.

Thanks! PM sent.

anyone?

As far as I know, you'll need to set it up using the 'Default User' profile... I don't think you can just add registry entries otherwise...

Use this code so that you aren't prompted regedit.exe /s "%SystemDrive%\Install\FRWMX\register_fireworksMX.reg"