Martin Zugec

Well, the basics R KillBits and RestrictedSites I use WFW, eTrust AV, KB&RS, SP2 (probably most important ) and looks like from next month will be betatesting MS antispyware solution

Microsoft now use Windows Update v5

It was like normal presentation, not paper document We were working for Microsoft and prepared few advanced deployment techniques and I met one MVP, that provided this information to me I remember RunOOBE (simplier to remember than UnattendSwitch), IndexCatalog and few other... I was presenting advanced boot medium techniques (auto NIC detection and configuration, auto gdisk detection, advanced dos menus etc.)

Then study Vbscript (with ADSI and WMI) is one of the most powerfull tools for administrator... Ok, in that case why not use RunOnceEx instead of batch files?

And it work? Strange, I though it is always inside i386... So maybe this will really solve charlo´s problem... Anyway thank for the information, maybe if I will need to make unattended cd I will find this useful

Heh, is sec a really big problem? In that casu use vbscript with wscript interpreter

Hiding cmd windows is best solution - use cmdow or autoit...

2totoymola: Nope... I dont know how on cd, but in network unattended installation it has to be inside i386 folder

Since I began using Monad I am really looking forward to Longhorn! Hope so there will be more technologies like this

It is undocumented Got it from one MVP presentation... It is teoretically the same as UnattendSwitch, but sometimes solve problems that exists wit US

Classic folder layout? What do U mean by this?

Btw about OOBE, try this trick: Instead of UnattendSwitch try RunOOBE=no

What kind of VPN connection? Have a look here first: http://unattended.msfn.org/xp/restore_dialup.htm

WMI is the core system for managing windows... From HW, processes, services to exchange... WMIC is WMI Console - it is shipped with Windows XP and W2k3 Server. It allow access to WMI even for people who dont like programming. For example command (in cmd.exe) "wmic process get name" will list all processes. "wmic process list brief" will show basic informations. "wmic process list full" will show all available informations. Check it Using wmic. exe /? U can see all available aliases. There is possibility to directly access WMI schema and add aliases, so there is great capability.

If U R sure U have correctly configured settings, run command "netsh winsock reset"

As I posted somewhere else, I think the best way is to find cdrom drive with cd, that have specific name, inside... Using WMI or WMIC it is not hard and U can be sure it will work

Well, if I understand right, U R not using right strategy - U should create typical unattended, but personalize OOBE for specific user settings (thats the way that companies like HP, Dell etc. use)

Hmmm, never had problem... I got autogenerated fdd and cds for tech guys in my company and they R using it quite often.

Ok, first things first... Can U try that OOBE solution I provided?

The files from $oem$\$1\Install will be copied to your local drive... There should be path c:\Install - can U see setup.cmd in that folder?

Sorry guys, why dont U use Enterprise Deployment Pack for WMP?

2blasted: Hope so this will solve your problem: to skip User etc. part (OOBE), U need to provide UnattendSwitch=yes... Instead U got UnattendSwitch="yes" Just remove quotation mark About second problem - after installation, can u see setup.cmd in that local folder?

You can find info here: http://www.spc.int/it/TechHead/unattended_..._third_part.htm

In ref.chm find [OEMBootFile]

Hope so this is not somewhere around in knowledgebase and someone find it useful... You can create boot drive to boot into Windows (tested on w2k and xp). This is specially useful, if U need to use your own boot.ini option (for debugging BSOD for example). Only thing U need to do is to copy this threee files to EMPTY formatted medium: ntldr ntdetect.com boot.ini U MUST copy the ntldr first! Then copy the rest of the files. And thats it! Simple and (for me) quite useful... The final boot medium is compatible with older OS, so boot medium from XP SP2 can be used to boot to w2k with no problems. If anyone can speak czech/slovak, you can find whole article in www.supersupport.org under boot.ini