SOLVED Is it possible to use SCCM to deploy windows update on workgroup computers

[Manuel]

Hi

I just having problem running an update to a bunch of Workgroup machines. Is it possible to use SCCM to deploy windows update on workgroup computers

I think the problem is the network account so I just want to know which is the sintax or format of the currect account user that I have to use in order to use to deploy windows updates

I mean, do I have to type IP\local administrator user account or do I use .\Local administrator user account

Thanks in advanced

Manuel

 

[Manuel]

Hi !

 

[Prajwal Desai]

To support workgroup clients, the following requirements must be met:

• During client installation, the logged-on user must possess local administrator rights on the workgroup system. The only account that Configuration Manager 2007 can use to perform activities that require local administrator privileges is the account of the user that is logged on to the computer.
  
• The Configuration Manager client must be installed from a local source on each client machine. This requirement ensures that a local source for repair and client update application will be available for the client.
  
• Workgroup clients must be able to locate a server locator point for site assignment because they cannot query Active Directory Domain Services. The server locator point can be manually published in Windows Internet Name Service (WINS), or it can be specified in the CCMSetup.exe installation command-line parameters.
  
• Workgroup clients must use the Network Access Account to access package source files on distribution points. If a Network Access Account is not configured, clients cannot access content on the distribution point. For more information, see Example Package Access Scenarios.

Although workgroup computers can be Configuration Manager 2007 clients, there are inherent limitations in supporting workgroup computers, including the following:

• Workgroup clients cannot locate their default management point from Active Directory Domain Services, and instead must use DNS, WINS, or a server locator point. DNS is recommended for workgroup clients. For more information, see Configuration Manager and Service Location (Site Information and Management Points).
  
• Active Directory system, user, or user group discovery is not possible.
  
• User-targeted advertisements are not possible.
  
• The client push installation method is not supported for workgroup client installation. For more information about installing the Configuration Manager client on workgroup computers, seeHow to Install Configuration Manager Clients on Workgroup Computers.
  
• Global roaming is not possible. For more information about client roaming capabilities and behavior, see About Client Roaming in Configuration Manager.
  
• Using a workgroup client as a branch distribution point is not supported. Configuration Manager 2007 requires that all site systems, including branch distribution point computers, are members of an Active Directory domain.
  
• The out of band management feature is not supported for workgroup computers. For more information about out of band management, see Out of Band Management in Configuration Manager 2007 SP1 and Later.

See More details:
http://technet.microsoft.com/en-us/library/dd547071.aspx

 

[Manuel]

Thanks Prajwal, I will check it and I'll let you know how it will result

 

[Prajwal Desai]

@Manuel - Any update on this ?.

 

[Manuel]

Please give me till Friday to re check it

 

[MrNetTek]

To support workgroup clients, the following requirements must be met:

• Using a workgroup client as a branch distribution point is not supported. Configuration Manager 2007 requires that all site systems, including branch distribution point computers, are members of an Active Directory domain.

While I understand what Microsoft says they support...how do we make a workgroup, non-domain, machine work as a DP anyways?

I am very close to solving it...as I'm not receiving errors with the workgroup DP. However, when pulling content from my primary site DP to the workgroup DP, the files...the content in replication...just stays "In Progress" forever. The only message I see that may help us is: package does not have a preferred sender.

 

[Manuel]

Well, I did not make it work with workgroup computers.

MrNetTek, Did you apply patch to any Windows computers in workgroup?
and did you think is necesay to make a boundary to any workgroup computer?

Thanks in advanced

Manuel

 

[MrNetTek]

Well, I did not make it work with workgroup computers.

MrNetTek, Did you apply patch to any Windows computers in workgroup?
and did you think is necesay to make a boundary to any workgroup computer?

Thanks in advanced

Manuel

I started by doing this: http://eddiejackson.net/wp/?p=14669

That is my website...

Then, I made sure I only used %computername%\Administrator on the creation of the DP itself. Getting workgroup computers to report in wasn't all that difficult...getting a workgroup computer to work as a DP has remained elusive, for now.

I think Microsoft has created the SMS class in WMI to only work with a domain account----BUT, because WMI security can be changed, that will be my next test. Just because Microsoft doesn't support something, doesn't mean it can't be done. I spend my days and nights doing the impossible. This is just my latest challenge.

Note, I 'did' create boundaries for all workgroup computers.

 

[MrNetTek]

I figured it out guys. A Workgroup can indeed run the DP role. I will be posting a full write up at my site.

This was the basic config...

1 Editing files for name resolution

2 Using %computername%\service account

3 Using IP address for FQDN name

4 Do not use PullDP

After setup, I tested software deployment and the software portal; both worked.

 

[MrNetTek]

Okay, here is the write up of how I got it to work:

http://eddiejackson.net/wp/?p=14988

 

[Prajwal Desai]

Thanks for the update.