Rocket Man Posted August 10, 2012 Report post Posted August 10, 2012 Hi Just wondering how deploying to WORKGROUP works. Is it possible to deploy to workgroup without having to add the configmgr client? I have a scenario where by numerous laptops do not need to be on the domain nor do they need to be managed. I have tried to deploy TS and specified to join WORKGROUP and have removed the component Setup Windows and Configuration (as i do not want the client on the laptops) But when it gets to the Setup operating System it bombs out with an error code.....but after a restart the laptop boots into windows and is also seen as an unknown computer in SCCM database. Is there a proper way to achieve this without it bombing out at this stage? Thanks Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted August 10, 2012 Report post Posted August 10, 2012 You will always need the step Setup Windows and Configuration, as it also sets up your Windows installation. The only way to "get rid of" the client is to uninstall it. Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted August 10, 2012 Report post Posted August 10, 2012 Thanks Peter Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted August 31, 2012 Report post Posted August 31, 2012 Hi Peter I have done this and now it does not bomb out....just wondering is there is some setting that I have to attach to the Setup Windows and Configuration to get it to install the full client...at the moment it is only installing half the client.........the WORKGROUP PCs show up in all systems as active and clearly shows they are in a workgroup in the properties of each. I have added SMSMP=SERVER.domain.xx to the Setup Windows and Configuration settings......but still only half client. Any ideas or is it not possible to fully manage workgroup machines? Thanks Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted August 31, 2012 Report post Posted August 31, 2012 I would start with looking at some logs, like the ClienIDManagerStartup.log Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted August 31, 2012 Report post Posted August 31, 2012 Ok Thanks Peter I just checked the client on the machine and actually it does have the self-signed cert but is still unable to find the site(it has the site code though)....and still only half the client installed without RMCCTRL service in task manager etc.... I am testing this on a batch of virtual hyper-V machines with a legacy NIC attached also....would this be the problem? Unfortunately i can not deploy to physical machines to test if any difference.. I checked the above log and the only failure i see is CCMCreateAuthHeaders failed (0x80004005) and failed to open to WMI namespace '\\.\root\ccmvdi' I also added these parameters to the client setup SMSLP=Server.domain.xx FSP=Server.domain.xx Still nothing! Thanks Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted September 1, 2012 Report post Posted September 1, 2012 Are you able to resolve the site servers name and/or fqdn? Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted September 1, 2012 Report post Posted September 1, 2012 By resolve you mean ping it etc.... Yes able to ping it both IP address ping and DNS name ping no problem..... if i enter in the site server name to browser URL i get the IIS page also...(these VMs are on a remote site than my PS server) Connectivity does not seem to be the problem. As i have said the workgroup VM does have a signed cert....... it is in all systems as active...but it does not have the full client, remote control etc...even though in the general tab of the client it say all components are installed.. Maybe it is because it is a VM with 2 NICs, one for PXE booting (legacy NIC). I am confused especially with connection to site server, and site code is also found by client but when i try to discover site in the client options in control panel it fails. Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted September 1, 2012 Report post Posted September 1, 2012 Also just to add Peter my structure is always intranet(not internet)...if this makes any difference?? I also have right click tools installed at PS. I turn off firewall on workgroup machine located at remote site and use the ping function of the rightclick tools and it pings no problem so that is now working both ways from client to server and vice versa...... One thing i am now noticing is when i try to use the Machine and policy retrieveal with the right-click tools it gives me the follwing error: They are showing up clearly as active in console: And as mentioned before the client has site code and i also add the properties during client installation of the DNSSUFFIX and SMSMP...... In the properties of the above 2 active machines the approved tab = 0 This should = 1 I checked this off my active domain systems properties that have no problems with policiy retrieval etc... Thanks Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted October 5, 2012 Report post Posted October 5, 2012 Dont mean to bring up an old thread...but has anyone any ideas what the solution could be on this problem?? I have found out it is not the Legacy NICs as I thought as I have deployed to physical machines and still the same outcome Thanks Quote Share this post Link to post Share on other sites More sharing options...
