Jump to content


rsarnold1s

Established Members
  • Posts

    4
  • Joined

  • Last visited

rsarnold1s's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Hi All, I have recently been looking at using the internet-based management functionality. My company has remote offices that are not connected via VPN and was hoping that this feature would help in the task of keeping inventory and such. I have a few questions about this: 1. My current setup is just a stand-alone primary site, can that also be used as the internet management point? 2. Would this work for deploying software and updates? 3. Do I just need to switch the client connection option to HTTPS? 3. I haven't run into any good guides on this, so if anyone has a link, please share! Thanks!
  2. I'm having a frustration issue with this. I edit the UDIWizard_Config.xml file to my specs, save it, update the MDT Settings Package, but it always defaults back to the orginal Wizard. I verified my changes are being saved and also checked the Content Status under Monitoring and my DP is updating the package, but it is using the default Wizard. Has anyone run into this issue? Ok I just realized the problem, I was updating the Settings package and not the Toolkit!.. Ugh!!!
  3. Hello All, I have recently deployed our new SCCM 2012 server and have been going through the awesome guides here to set-up the roles. I am running into an issue however, discovered systems are not automatically getting the SCCM client. CCM.log on the server doesn't show anything, it doesn't even attempt to install the client on the computers. However, if I do a right-click > Install Client, CCM.log shows that it detected the system and will install the client just fine. Things that I have checked: - The account that is specified to install the client can access the admin$ on the computers - I have set the client installation settings to "Enable automatic site-wide push installation" - Boundries are set correctly (The computers show in the console) I find it strange that the CCM.log doesn't even show an attempt to install the client on these machines. I have waited for almost 24 hours just to see if it is some timing issue, but nothing has changed. Install Client option works like a charm so I am at a loss here as to why it doesn't even attempt to auto install. Has anyone else run into this issue? Thanks in advance. CCM.log normal activity: Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 8/10/2012 9:59:26 AM 4020 (0x0FB4) The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Default MP: SCCM.acumen.net SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Certificate Store: SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Checking configuration information for server: SCCM.ACUMEN.NET. SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Install on DC: False SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:00:11 AM 3956 (0x0F74) The Site Control File has not changed since the last parameter update. SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Default MP: SCCM.acumen.net SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Certificate Store: SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Checking configuration information for server: SCCM.ACUMEN.NET. SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Install on DC: False SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:20:11 AM 3956 (0x0F74) Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:29:26 AM 4020 (0x0FB4) Sleeping for 60 minutes for queue "Retry". SMS_CLIENT_CONFIG_MANAGER 8/10/2012 10:32:26 AM 4024 (0x0FB8)
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.