briank1986

OK, change of plans. I decided to just make a screen saver and make a script to copy the .scr file into system32 and set the registry to use this screen saver. I also set the registry time out for 1 second that way the screen saver will appear almost right away letting the user know that it is re-imaging. Here is the VBScript if anyone needs to do something like this... On Error Resume Next Dim objShell, RegLocate, WshShell Set WshShell = WScript.CreateObject("WScript.Shell") destdir = WshShell.ExpandEnvironmentStrings("%windir%") Set FileSystemObject = CreateObject("Scripting.FileSystemObject") FileSystemObject.CopyFile "<PLACE YOUR .SCR FILE NAME HERE>", destdir &"\system32\" Set objShell = WScript.CreateObject("WScript.Shell") RegLocate = "HKEY_USERS\.DEFAULT\Control Panel\Desktop\ScreenSaveTimeOut" objShell.RegWrite RegLocate,"1","REG_SZ" RegLocate = "HKEY_USERS\.DEFAULT\Control Panel\Desktop\SCRNSAVE.EXE" objShell.RegWrite RegLocate,"wach.scr","REG_SZ" WScript.Quit

I'm running it with PSexec's "-s" switch, which runs it as SYSTEM. Using a Remote Task Manager tool I have, I verified that mshta.exe is running as "SYSTEM"... Still, nothing on the screen...

Hello everyone! I have an .hta file that needs to be run at the WinXP login screen. It's simply just some graphical text with our company logo to let users know to NOT touch the PC while it is being re-imaged... I'm having some trouble trying to get this .hta to show in this environment (login screen). For test purposes, I'm using PSexec to launch the .hta file remotely (obviously, I can't do it from the target PC due to it being at a login prompt). mshta.exe is running as a process on the target PC, but nothing is on the screen, I've tried using the -s and -i switches but had no luck...As soon as I log into the target PC, the .hta files graphic is visible on the screen... It has to be some environment restriction, I've seen other things ran at the logon screen but never knew how to do it. If anyone can chime in with any ideas, it will be greatly appreciated! Thanks, Brian.

Hello All! Well, I have a bit of a weird problem. Here it goes: I'm trying to get the extended desktop piece to re-enable after our ZTI OSD is complete, using USMT 2.6. Using registry key: HKLM\System\CurrentControlSet\Control\Video\=*. When I run the Scan/Load locally, after a restart the extended desktop piece is re-applied. Now the problem is, after running our ZTI OSD process the extended desktop piece does not re-apply.... I can't seem to figure out why, I was thinking maybe when USMT is trying to run LoadState before the drivers are not "Set" completely for the dual monitor video card????? By the way, we inject the drivers via WMI script. Any input will be greatly appreciate. If anyone could suggest a better way to go about this than using USMT, be my guest. I was thinking about hard coding the setting with a script, but I'm not much of a scripter... Thanks in advance! Brian.

Hello All! Well, were upgrading to USMT 3.0 from 2.6 in a couple of weeks. I have all the .inf files configured the way I need them from our current version, 2.6. USMT (User State Migration Tool) 3.0 uses .XML files in place of the .INF files.... I need a way to convert all my .INF files to .XML . Does anyone know how to do this quickly? I have looked for a converter but had no luck. Any input will be greatly appreciated!!! Thanks in advance, Brian.

Thanks for your input guys!!!!!! I had to use this switch - net stop ipnat - instead of wpeutil. I knew there was just one little thing missing....Why couldn't I have thought about the Firewall thing?? I really appreciate your posts! If this won't make the security guys happy, I might try the PC Anywhere thing! Thanks Again! Brian.

Hello all! This is my first post on this web site. I have recently been asked at work to find a way to connect remotely to WinPE. We use it in an OSD environment for WinXP. What I mean by "Remote Access" is - to simply be able to type a UNC path to access the WinPE build or to be able to completely remote control WinPE. I know WinPE has built in networking for outgoing connections, but is there a way to enable incoming connections? You can ping from the WinPE box but you can't ping the WinPE from an outside system. Any help or links to where I can find the answer will be greatly appreciated! Also, I have checked out a couple of different posts like this one: http://www.911cd.net/forums/index.php?showtopic=8420. I have done this process and can successfully get this to work in an actual Windows XP environment, but not in WinPE. There seems like there is just one thing missing but I just can't put my finger on it, does anyone have any suggestions as to an extra step I may have missed? Thanks, Brian.