Peter van der Woude

Does the smsts.log say anything about it?

They will keep their names.

You can continue without installing WSUS. WSUS is only needed with setting up a Software Update Point.

It is very easy and straight forward deploying Windows 7 with SCCM R2 SP2 (Beta) on virtual machines and on different hardware (laptops) Most of the drivers get detected and the rest most of the time even works with Vista drivers.

Not every program knows that parameter.... I think your best shots are as Naill suggested appdeploy.com, or google, or the manufacturer of the program.

Did you check the firewall on the client machine?

You are having a different problem now. The SMSadmin account can connect (Connected to administrative share on machine pama2008.pama.org using account 'pama2008\SMSadmin'). Your new problem is: Unable to connect to WMI on remote machine "PA5141", error = 0x80070005. I think you have to allow remote WMI connections through the firewall of the client (or put the firewall out)

The picture shows a group SMS Admins, but not the account 'pama2008\SMSadmin' that you use during the installation...

Depends on what package it is... You can try if it has a silent install by running on a testmachine the command "<program>.exe /?". When it has a silent install it will show it (most times the command is /s).

Correct, when you Active Directory Site is your Boundary you can only Advertise to clients within your Active Directory Site When it was standing on rerun it was causing your problem.

Yes it is possible, in fact I'm running my testenvironment in Hyper-V. I also used virtual machine to create my workstations image and I didn't need to add any drivers to my bootimage.

But what are you trying to achieve by getting the domain as a variable? If you can explain that, maby there is an easier way to achieve your goal...

LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account mdis\clientinstall --> Your installation account has to be local admin on the machine

As long as you are in the Task Sequence you run as a system account (except when you use a Run Command Line step with a Run as account) and then you can't access user variables like %USERDOMAIN%. As far as I can remember the DefaultDomainName regkey doesn't have to excist at that moment. If does already excist it doesn't have to contain the domainname, it can contain the local machine name to... But why do you want to get the domain name that you already know, because you just added the machine to the domain???

I read "No MP Certificates", maby this link might help: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/0b0a5940-cf66-414a-8e93-997215667cbd And otherwise I think of two things: 1. Is see two different ip ranges: 172.16.1.16 and 172.18.5.128 can they reach eachother? 2. Is your Network Access Account locked?

About your first post: I think you have to check your boundaries. When I read that there pops up an advertisement when you join the computer to the domain, I think that your domain is your boundary. SCCM will only advertise to computers inside its boundaries. About your second post: I think you have to check your advertisement settings (Tab schedule > Program rerun behavior).

Let us know if installing SP2 changed anything in your situation.

You can rerun the advertisement. See also: http://technet.microsoft.com/en-us/library/bb681010.aspx

That's indeed odd... with a default installation it should be there... But you can create it yourself to. You can use the following code/ text and save it as smsclient.sms on your harddrive. Then just browse from the wizard to the location where you saved it and your done [PACKAGE DEFINITION] LANGUAGE=ALL COMMENT=IMPORTANT - It is recommended that BITS is deployed prior to client upgrade. Please read documentation for information. VERSION=4.0 NAME=Configuration Manager Client Upgrade PUBLISHER=Microsoft PROGRAMS=SInstall [sINSTALL] WIN NT (X64) MINVERSION1=5.20.0000.0 WIN NT (X64) MINVERSION2=5.20.3790.0 WIN NT (X64) MINVERSION3=5.20.3790.0 WIN NT (I386) MAXVERSION1=5.00.2195.4 SUPPORTEDCLIENTS=Win NT (I386),Win NT (IA64),Win NT (x64) ADMINRIGHTSREQUIRED=True WIN NT (X64) MINVERSION4=6.00.0000.0 WIN NT (I386) MAXVERSION2=5.10.2600.2 WIN NT (I386) MAXVERSION3=5.20.9999.9999 USERINPUTREQUIRED=False WIN NT (IA64) MAXVERSION1=5.20.9999.9999 WIN NT (I386) MAXVERSION4=5.20.3790.2 WIN NT (I386) MAXVERSION5=6.00.9999.9999 COMMENT=IMPORTANT - Please refer to product documentation to determine the correct ccmsetup parameters. WIN NT (I386) MINVERSION1=5.00.2195.4 WIN NT (I386) MINVERSION2=5.10.2600.2 COMMANDLINE=CCMSETUP.EXE /noservice SMSSITECODE=AUTO WIN NT (X64) MAXVERSION1=5.20.9999.9999 WIN NT (I386) MINVERSION3=5.20.0000.0 WIN NT (X64) MAXVERSION2=5.20.9999.9999 WIN NT (IA64) MINVERSION1=5.20.0000.0 WIN NT (I386) MINVERSION4=5.20.3790.0 NAME=Advanced Client Silent Upgrade WIN NT (X64) MAXVERSION3=5.20.3790.2 WIN NT (I386) MINVERSION5=6.00.0000.0 WIN NT (X64) MAXVERSION4=6.00.9999.9999 CANRUNWHEN=AnyUserStatus [PDF] VERSION=2.0

Can you try to describe what exactly happens and when it goes wrong? And can you maby post a bigger part of the smsts.log so we can see what happens?

When you select the folder where your packages are in, then you will get a list which includes Package ID

This screen is logic after a reboot, it will go away after you select "Clear Last PXE Advertisement". But I think your problem is before that. What axactly happens before the restart?

And that where the Vista versions of the drivers that you added to the bootimage (because the bootimage is Vista-based)?

This sounds like that you don't have the correct networkdrivers in your bootimage.

What do the logs (LocationServices.log & ClientLocation.log) say on the clients that are not reporting to ConfigMgr?