Asked by:
Network discovery does not detect OS on workgroup computers

Question
-
Hello
I'm somewhat new to SCCM 2012, but have rolled out the client to most of my domain computers, along with endpoint protection. I'm trying now to setup discovery and auto client deployment to our retail enviroement, which is firewalled and not on the domain. I think i've got the firewall ports open, as i'm able to push the client to a few computers that are on the domain, and behind that firewall. Using AD system discovery.
The problem is when i setup network discovery to search a few subnets to start. It'll find the systems, but can't seem to connect to system to determine the OS. When i look at the logs, it seems to be using an anonymous account to connect to the IPC$ share, and then it fails and says can't deteremine OS. I have an account in my client push list that is basically %computername%\adminaccount but it doesn't seem to try this account. When I look at a network capture on the device that it's trying to discover, it seems to be attempting to query the computer with the SCCM computer account itself, which doesn't make sense. Can anyone shed some light on what may be happening?
Here are a few lines from my netdisc.log file:
ADM: Established connection to \\st2110-pos01\IPC$ using anonymous account
ADM: Failed to establish connection to \\st2110-pos04\IPC$, error 1326
ADM: NtBrowser: Failed to retrieve OS info from device st2110-pos04, error 5.
I think if it would query IPC using my admin account for the workgroup computers, it may succeed, but it doesn't seem to be trying.
Thank you
Wednesday, April 3, 2013 2:32 PM
All replies
-
Hi,
Workgroup computer needs to be handled differently. You require to install the client manually or using script.
You can refer to http://blogs.technet.com/b/anilm/archive/2012/05/06/managing-workgroup-clients-in-configuration-manager-2012.aspx
Regards,
HauWednesday, April 3, 2013 2:40 PM -
Thank you for that, i haven't attempted to install it manually yet, because another SCCM expert pointed me in the direction of this article, which says you can do a client push to workgroup computers, if i could get the network discovery to work properly.
Wednesday, April 3, 2013 2:49 PM -
Cool!!!
Error code 1326 means username and password incorrect. Are you sure that all your Workgroup computers have the same local admin username and password?
Wednesday, April 3, 2013 3:04 PM -
client push also worked prior to CM12 (not supported, but the client push account could be a local account). Now you need a manual process, do you have Orchestrator in place? then you can create a run book that will copy the client files locally, perform the installation and delete the client files Again.
Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund | Mastering ConfigMgr 2012 The Fundamentals
Wednesday, April 3, 2013 3:05 PM -
Yes, and i've verifed connectivity using the test tool (where you add the account) but as I indicated, the logs report sccm as trying to connect to IPC$ with an anonymous account.
Kent;
No i don't have orchestrator in place, but may be able to deploy it another way. If i could access the SMS_SITENAME share on the sccm server, it's giving me access denied, should I manually edit this share or is there a way to do it cleanly thorough the admin tools?
ThanksWednesday, April 3, 2013 4:45 PM