Martin Zugec

As I said in another thread - dont to it this way, use WMI instead...

Check out my scripts for this purpose (I posted them some time ago)... For you the PnPBased would be better than PCType...

Nope, you can only use quickedit or context menu as ringfinger said... Customizable shell will be introduced with Vista family.

Of course www.sysinternals.com However most of the advanced stuff I am doing through internal WMIC...

Are you using CD or network installation? This was common problem with emm386... Just run the installation and give it some time (maximum timeout I saw was 2 hours)

If you are using PE (WinPE/BartPE), you can create simple script... In you unattended.sif, create Computer=**ComputerName** Now pick some utility for replacing text and replace **ComputerName** with variable %Random%...

Its not really nice way to do this through registry - you can use command Wmic nicconfig set SetMTU instead

Its not easy to perform this using internal commands, it is much easier to download some external utility to do this...

FYI: I changed blog to http://msmvps.com/martinzugec

Sent to your mail... Hope so we will see it from you ASAP Martin

Yep, I have same opinion as Takeshi...

Hi GSM! I was all the time thinking about APIs and .net classes, that I forget about wmi classes! Thanks, I will work on it (or you can, if you would like to help)...

In that case post WindowsUpdate.log (not Windows Update.log)

Ok, now it looks fine... You can try this script, that will force client: WSUSForce.cmd @echo on net stop wuauserv REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v LastWaitTimeout /f REG DELETE "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v DetectionStartTime /f Reg Delete "HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" /v NextDetectionTime /f net start wuauserv wuauclt /resetauthorization /detectnow @echo off

Can you post output from cleint diag again + export registry configuration?

"ScheduleInstallDay"=dword:00000000 should be ScheduledInstallDay! UseWUServer must be 1 if you want to use WSUS Also enable RescheduleWaitTImeEnabled... But your biggest problem is UseWUServer...

Looks fine... Switch UseTargetGroup to 1 and create Test Group on WSUS server.

I am looking for someone that is able to create utility to schedule one task + share folders... Anyone?

Ah, m4dh0 was faster

You can download it from here: http://www.microsoft.com/windowsserversyst...ds/default.mspx Let me know the results... Martin

What can you see a.) when you run wsus client diagnostic? b.) in windowsupdate.log after you run wuauclt /resetauthorization /detectnow?

I will now talk about Default packages. You can see them in Main.ini... What are they? Default packages are in my opinion really nice idea, that make SDS open to further modifications... We can say they are acting like plugins... There are two different default package types - Start and End. The default packages are "around" every job - for example if you run job AdobeReader, all SDS.Global.DefaultPackages.Start.# will be performed BEFORE AdobeReader and all SDS.Global.DefaultPackages.End.# will be performed AFTER AdobeReader. As I said it is quite useful for plugin functions - for example I am using SDS.Global.DefaultPackages.Start.3=Command:Disable_Input and SDS.Global.DefaultPackages.End.3=Command:Enable_Input This will perform command Disable_Input before installation and enable input after installation. This example will block user input (mouse+keyboard) for duration of installation. In fact DefaultPackages are really easy to implement/understand... Any questions?

Dman agreed to create Package generator GUI! Welcome to team man

You can use BITSAdmin... It is in support tools and maybe in RK.

Eee, what are you trying to achieve? Test if google is available? BTW syntax is correct.