This question i don't believe has been asked. I've read http://forums.wsusoffline.net/viewtopic.php?f=4&t=563&start=10&hilit=installer+task+schedule and have a question. in that post it was mentioned that the main hold back to why you can't autorecall for a network share is because the shared mapped drive isn't shared to all user profiles so when it reboots the share is not available. Is there a way we can manipulate the autologin code to temporarily autologin to the admin account (we have to supply the necessary username and valid password of course) instead of the WOUTempAdmin account? I mean if we map the software to the valid network share via the admin account initially couldn't we just force the system to auto login to the current account the drive was mapped and then just reboot to that account so it's available to the software again?
Either that or on the autorecall command after reboot into the WOUTempAdmin account couldn't we just add a line of code that remaps the drive before tryin the updates?
I've noticed that after running the offline utility to update windows 7 systems and xp systems that the share is still available if i log back into the admin account. And also that if i call the doupdate command properly that the system takes off again without a hitch. Maybe this is a oversight on my part.
And one other thing, on some systems the autorecall actually finds the folder after reboot (not sure how, sometimes it doesn't and just hangs up, i can't recreate it reliably yet) it asks for a administrator name and password. Is there a way i can hard code that into the script anywhere?
Thanks.