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 Thursday, March 26, 2015 1:18 PM

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

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator 22 hours 6 minutes ago
• Marked as answer by Samus-Aran 15 hours 19 minutes ago

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

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Thursday, April 02, 2015 9:36 AM
• Marked as answer by Samus-Aran Thursday, April 02, 2015 4:23 PM

So the problem was that I imported the computer information in before hand when using stand alone media which was the cause why the computer could not register.

Thanks for the help!