TheManager02

Well, when all else fails in my research I come to the Master for answers. I have a request for supporting linux and unix from a client. Somewhere along the line someone has explained that CM12 R2 out the box will update linux and unix. Does anyone have any thoughts they can share regarding this notion? If there is any documentation? I do have the client installing, had to make some adjustments for locations of the installation, yet all is collecting what I believe to be the correct information of hardware and software. Thank you in advance.

Failed to mention-when using the MAC address the task sequence works like a champ, as expected.

Good afternoon, CM12 is up and running, applications deploying, SUP/WSUS working perfecting. Time for OSD testing...requirements: 1. Client wishes to use PXE 2. Manually importing devices using GUID 3. Using 1 Collection for added devices using Collection Membership Straight forward, until I begin testing. Testing scenario- 1. Create CD bootdisk (did want to troubleshoot PXE without knowing CD boot worked first) 2. Create a Collection (TEST-Collection01) 3. New laptop out of the box 4. Import new laptop into CM12 using GUID 5. Once seen in All Systems (I know we can move the device directly into my test Collection, stepping through to validate each step works) 6. Power up laptop on the network using CD boot 7. Cannot find a Computer Policy So-back to drawing board. I then decided to test Importing the laptop using the MAC address. I followed all the steps exchanging Step 4 with using the MAC address. I have attempted this with another system and have had the same results. Does anyone have any thoughts on this issue? OS level=W server 2012 R2 ConfigMgr=2012 R2 Task Squence is basic, wipe drive, install OS (Win7SP1x64) on laptop Thank you in advance for any thoughts.

Where can a guide for Win Server 12 and CM12 WSUS and SUP full configuration be found? That is what I'm missing most likely. Thank you.

· Good morning-I have followed every article I can possibly find and admit defeat at this point. CM12 SUP is not syncing correctly, not WSUS on Server 2012. I have installed Primary site on a Windows 2012 R2, SQL 2012 (All updates) and CM12 R2. SQL server is an external clustered setup from the Primary site. I have verified IIS ports are correct. Any help resolving this will be greatly appreciated. This area seems to a pain point for many folks. WSYNCMGR.LOG Sync failed: WSUS update source not found on site XXX for configuration error details.. Source: getSiteUpdateSource SMS_WSUS_SYNC_MANAGER 1/3/2014 9:54:10 AM 6112 (0x17E0) STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVERNAME SITE=XXX PID=5244 TID=6112 GMTDATE=Fri Jan 03 14:54:10.560 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site XXX. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 1/3/2014 9:54:10 AM 6112 (0x17E0) Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 1/3/2014 9:54:10 AM 6112 (0x17E0) WCM.LOG Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:54:20 AM 5968 (0x1750) WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:55:20 AM 5968 (0x1750) WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:56:20 AM 5968 (0x1750) WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:57:20 AM 5968 (0x1750) Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:15 AM 5968 (0x1750) Attempting connection to WSUS server: SERVERNAME, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:15 AM 5968 (0x1750) Successfully connected to server: SERVERNAME, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:15 AM 5968 (0x1750) Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Attempting connection to WSUS server: SERVERNAME, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Successfully connected to server: SERVERNAME, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SERVERNAME SITE=XXX PID=5244 TID=5968 GMTDATE=Fri Jan 03 14:58:23.903 2014 ISTR0="SERVERNAME" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) StateTable::CState::Handle - (6603:3 2014-01-03 14:58:23.903+00:00) >> (0:0 2013-12-31 19:42:27.368+00:00) SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='26010DEB-B7D1-4105-8B6B-74DBD5CFEB72' SID=6603 MUF=0 PCNT=2, P1='XXX' P2='2014-01-03 14:58:23.903+00:00' P3='' P4='' P5='' SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) CStateMsgReporter::DeliverMessages - Created state message file: D:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\d65p6158.SMX SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Successfully send state change notification 26010DEB-B7D1-4105-8B6B-74DBD5CFEB72 SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750) Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 1/3/2014 9:58:23 AM 5968 (0x1750)