Jump to content


ercole77

deployed computer remains unknown

Recommended Posts

Hi guys

i have this problem with SCCM deploy phase.

 

A deployment to unknow computers using PXE...the process begins, and i see a "unknow" computer under SYSTEMS.

 

When all is done i see the final computer name MININT-* with client installed NO and inactive but the UNKNOW computer still remains on the console. Looks like the unknow has to be renamed or something else but doesnt occour.

 

On the just deployed client itself i see only few Actions under Config mgr client.

 

 

Am i missing something?

Share this post


Link to post
Share on other sites

UPDATE in ccm.log i have

 

 

---> Attempting to connect to administrative share '\\MININT-KU3QBND\admin$' using account 'domain\account' SMS_CLIENT_CONFIG_MANAGER 01/06/2012 15:31:09 4724 (0x1274)

 

 

 

---> ERROR: Unable to access target machine for request: "2097152087", machine name: "MININT-KU3QBND", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 01/06/2012 15:31:52 4724 (0x1274)

 

 

 

i changed sensitive info with domain\account but this is a domain admin how is possible it cannot connect to admin$?

..

Share this post


Link to post
Share on other sites

another UPDATE......during deployment if i press F8 i can ping hosts by name and by ip. BUT i cannot ping the deploying machine itself from other hosts. Name is registered in DNS and regularly resolved but machine is not pingable..cannot understand WHY

Share this post


Link to post
Share on other sites

How does the "Setup Windows and ConfigMgr" step look like in your TS? Did you change the default package? (see step5 in http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/)

 

You say you only got a few actions in the client, so I actually assume the installation went through. Did you check to see if the site code is detected correctly? Also, you might try to update the collections memebership as I've seen that help in some cases where you only got a couple of actions in the client, although it souldn't really be needed since you installed the client during OS-deployment..

Share this post


Link to post
Share on other sites

Did you perform a domain join with the machine during the OSD? You should also set the machine name in your TS to something reasonable.

Share this post


Link to post
Share on other sites

hi thanks for your reply.

Yes i created the configclient package exactly as that useful guide says. Installation was perfect, and i can see SITE code correctly; i performed domain join.

 

Now i have checked and unknow client disappeared, i see one MININT-xxx with client installed yes and another MININT-xxx (the same) with client installed no.

I think im missing something or something goes bad when client is deployed.

I cannot get rid of this error

 

-> ERROR: Unable to access target machine for request: "2097152087", machine name: "MININT-KU3QBND", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 01/06/2012 15:31:52 4724 (0x1274)

Share this post


Link to post
Share on other sites

Try to connect manually to the admin share of the client with the same and with a different a account. Verify the password for the push installation account. Make sure the client firewall is configured correctly. Also check your DNS/DHCP configuration, does reverse lookup work?

Share this post


Link to post
Share on other sites

Im going to check if admin$ share is reachable during sccm client deployment. Is there something about firewall i can verify? I cannot ping the client at this moment during this phase if the task.

Share this post


Link to post
Share on other sites

here is ccm.log during client install on a client.

I have verifyed DNS and reverse lookup. During the install i executed pressing F8 "netsh firewall set opmode disable"

 

Without firewall it works but i have duplicate id in console, one with client installed YES and nother with client installed NO

ccm.log

Share this post


Link to post
Share on other sites

Duplicate entries are normal, because SCCM will create a new object during OSD (different hardware ID). The obsolete object will be deleted automatically, if the client has been registered correctly before in SCCM. If not you have to delete the outdated entry manually.

Share this post


Link to post
Share on other sites

You're welcome.

 

This depends on the schedule of your maintanance tasks and on the update cycle of your collections. Usually it's no problem though, because the old record is set to obseolete and will be delete according to your maintanance task (if its is configured?). Check the default values and lower them if needed. Update cycles for collections can be set to 1 hour without problems (default is 1 day). Don't know the default value for the cleanup task now. But the default is usually OK.

You should check for invalid duplicate entries now and then though. They may be imported through the AD discovery. Happens pretty often for laptops in our environment when they have not been deployed with SCCM OSD. After a half year of travelling around the world they come back and get reimaged, but the old record stays forever until it gets deleted manually.

Share this post


Link to post
Share on other sites

found description of the problem

 

http://blogs.technet.com/b/configmgrteam/archive/2011/08/17/known-issue-and-workaround-duplicate-records-when-you-use-unknown-computer-support-with-active-directory-delta-discovery.aspx

 

So i received duplicate record because i had these OU

 

- OFFICE1 (inside department OU)

- OFFICE2 (inside department OU)

- DEPLOY

 

Deployed PC go in DEPLOY OU. Active directory System discovery was set to these 3 OU so a record was created by this and another by hearthbeat discovery.

 

Now i have deselected AD system discovery on DEPLOY OU so duplicated pc are avoided.

 

The problem is: after a new pc is deployed i need to manual perform a cycle to make pc appears in asset.

 

What's the best way to avoid this?

Share this post


Link to post
Share on other sites

Solved, i disabled Active directory system discovery and added to task sequence this script to forc a cycle

 

 

actionNameToRun = "Request & Evaluate Machine Policy"

 

Dim controlPanelAppletManager

Set controlPanelAppletManager = CreateObject("CPApplet.CPAppletMgr")

Dim clientActions

Set clientActions = controlPanelAppletManager.GetClientActions()

Dim clientAction

For Each clientAction In clientActions

If clientAction.Name = actionNameToRun Then

clientAction.PerformAction

End If

Next

 

Now works like a charm. Thanks to everyone!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...