burgemaster Posted July 15, 2013 Posted July 15, 2013 (edited) Just thinking aloud. We have 600 machines to reinstall with windows 7 this summer. I have wds/deployment manager setup so all it needs is an F12 to pixie boot and the rest is automated. I just wondered from XP is it possible to remotely send a command to reboot into a pixie boot environment? Or remote in and load the boot.win? Basically want to do the whole school sat as my desk!!! Edited July 15, 2013 by burgemaster
eddyc Posted July 15, 2013 Posted July 15, 2013 I don't think you can do this from WDS directly. I think if you use SCCM and push the client out to all of the machines, you can then schedule a workflow to make them reboot and reimage by themselves without leaving the office! We still are working on migrating from WDS to SCCM so if you do find a hands free way of starting the imaging remotely, please let me know! eddyc
FN-GM Posted July 15, 2013 Posted July 15, 2013 The PXE thing is based on the hardware. What type of machines are they? Its possible to do it with Dell. SCCM is the way to do it, but then will be a little work for you.
burgemaster Posted July 15, 2013 Author Posted July 15, 2013 Dell and lenovos.. Will leave the sccm install .. Only 4 days left. I'm guessing dell have a broadcast command to wake them from off into pixie?
FN-GM Posted July 15, 2013 Posted July 15, 2013 If they are dell optiplex you might be in luck. There is a tool to use to temporary change the boot order for 1 boot to PXE. It can be done remotely. Then you somehow trigger a remote reboot for it to apply.
MordyT Posted July 16, 2013 Posted July 16, 2013 Interesting. We always set pxe to boot first in the bios. Would love to know how we can change the boot order remotely
jugglerjoe Posted July 16, 2013 Posted July 16, 2013 Right. I have just done this without SCCM for upgrade from 7 to 8. In the MDT Make a generic task sequence with minor changes. One that can do Replace\New Computer\Refresh Deployments. Now i need to warn that this is not best practice at all but i found it worked for me. In your Task Sequence for the upgrade in the State Capture part, inbetween the Capture Network Settings and the "Refresh Only" Folder add in a task sequence variable step. I named Mine upgrade and made it Equal to "YES". Then on Refresh Only folder Remove the DeploymentType variable filter and add your upgrade one. (Do that on both Refresh Only folders). In the Preinstall part i have disabled all 3 of the folders of "New Computer Only" + "Offline User State Capture" + "Refresh Only". then add whatever you want. I didn't find this way i did get a few boot errors on first boot and had to F12 some anyway but the majority seemed to work. then to launch it. Make a fully automated Customsetting.ini (but don't overwrite the one you use now). If you want to keep the current computer names in the CS.ini put OSDComputerName=%computername% and stuff like that (or use scripts if you really wanna) then to do it properly google for psexec and download it. then use the psexec program to execute this on remote computers. (alt u can use remote powershell etc etc) \\\\Scripts\LiteTouch.vbs /rulesfile:CustomSettingsWin7To8Upgrade.ini hope that helps =]
jugglerjoe Posted July 16, 2013 Posted July 16, 2013 As for @MordyT i believe HP/Dell Machines have this capability but i have not heard of any others. Unless you run a bois update with a bois file through a startup script maybe but i am unsure.
ChrisH Posted July 16, 2013 Posted July 16, 2013 It's a shame your not using MDT as you can launch a MDT sequence from windows by going to the share and executing litetouch.wsf. You could do this on multiple computers using psexec or something like that.
burgemaster Posted July 16, 2013 Author Posted July 16, 2013 Just what I needed!! We ARE using MDT !! Thanks will try this in the morning! Maybe devise a startup script or something Thankyou
jugglerjoe Posted July 16, 2013 Posted July 16, 2013 @ChrisH That's exactly what i said >_< but with steps on the Task sequence Indeed a startup script should work, not tried it tho =]
ChrisH Posted July 16, 2013 Posted July 16, 2013 @ChrisH That's exactly what i said >_< but with steps on the Task sequence Indeed a startup script should work, not tried it tho =] Sorry I read SCCM and skimmed the rest 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now