Hi!

I have some remote locations where I use Stand-alone media to install the computer cause the WAN is to slow to transfer the image and application over it. I see some problems with this.

The first problem is that it does not connect to the SCCM-server to during installation which means that it does not get the correct computer name. I have solved this with a script that prompts for a computer name.

The second problem is that when the installation is complete it does not register itself so I most re-install the agent for it to register. Is this by design or is something wrong?

If it is by design then there should be another media type, "Content media" which you can just put packages, applications, drivers and images into but during installation, let the client download the rest of the information from the site server. e.g, task sequence, computer- and collection-variables, join the domain etc...

Thanks!

• Edited by Samus-Aran 18 hours 27 minutes ago

First, stand alone media contains everything you need to deploy the os - that is the point.  So, the statement about "it does not connect to the SCCM-server" needs some more explanation.  Why would it need to connect to the SCCM server to name the computer properly?

Examine your smsts.log files and determine if errors are occurring.  FOr the failed client install, also check the smsts.log as well as ccmsetup.log in c:\windows\ccmsetup

Jeff

Hi!

"it does not connect to the SCCM-server" means that it does not check if an task sequence is advertised for it.

Even though I have imported the computer information for the computer with MAC and computer name it does not use that name, it joins the domain with name MININT-XXXXXXX. (Solved this with script that prompt for computer name  and set variable OSDComputerName)

Does not look for computer- or collection-variables, I have to specify these when I create the media. 

To clarify, the installation of the agent does not fail, it installs fine and using it to install all applications specified in the task sequence but afterwards, it does not register with the SCCM-server so in the console I still see it as non-active, Client = None.

Was does the  ClientIDStartupManager.log show on the affected client?  And to clarify, if you simply reinstall the client it registers fine?

Are there differences in the command lines used to install the client in your TS Media versus the manual install?

Ok, if you are using stand alone media, by design, it is not going to contact the ConfigMgr site server/MP.  So, yes you need a script or some other mechanism to name the PC.

For the client issue, check the clientidstartupmanager.log as was mentioned.

Jeff