Search the Community

Ok, so now that SP1 is out I've wanted to give it a few days and let others do some of the heavy lifting before I jump in Upgrading CM2012 to SP1 seems fairly straightforward enough, but I had some other questions: What about upgrading to SQL 2012? We're currently on 2008 R2, and as long as I'm updating software, then I figured I should at least consider this. Is there anything I need to know before upgrading my SQL version? What about CM client updates? We only have a primary server in our environment, and I noted that the option to automatically upgrade clients under the site hierarchy settings was greyed out...I assume this is because we only have a primary site and no CAS. So how are people handling their client updates? Incidentally, our WSUS is controlled by a third-party up-stream server, and I can't manage those settings. I'm also looking at bumping up the OS to Server 2012 at this time as well...like the title says, there are a lot of updates about to take place. Any input is appreciated!

I am having a difficult time trying to get the client installed on XP machines that have an older client on them. I know I am overlooking something, I just can't seem to see it. I am running SCCM 2012 SP1 Here is some detailed information from one of the client machines Windows XP SP3 (it did have the SCCM 2007 client installed and was pointing to a different site that was no longer in use) This is the info I have after SCCM 2012 deployed the new clients Shows the Version as: 5.00.7804.100 Client cert: None Connection Type: Unknown Site Code is empty Network is empty Actions only has: Machine Policy Retrieval & Evaluation Cycle User Policy Retrieval & Evaluation Cycle I even tried to manually install the client with: "\\zeus.gwusd.org\SMS_Z01\Client\ccmsetup.exe" /mp:Zeus.gwusd.org SMSSITECODE=Z01 SMSSLP=Zeus.gwusd.org SMSMP=Zeus.gwusd.org DISABLECACHEOPT=TRUE DISABLESITEOPT=TRUE Ccmsetup.exe ran for 30 minutes, but the settings were the same. I attached both the ccmsetup.log and the client.msi.log Thanks! ccmsetup.log client.msi.log

Hey everyone, Happy survival of the Maya end of days! hehe. I've been looking at the SP1 beta of sccm 2012 in my lab, and also read up some on it, and i found some information that says the following: "More flexible hierarchy management with support to expand a stand-alone primary site into a hierarchy that includes a new central administration site, and the migration of a Configuration Manager SP1 hierarchy to another Configuration Manager SP1 hierarchy. (Source: http://technet.micro...ibrary/jj591552) From what i can understand, this means that you should be able to join a hierarchy currently only using a Primary Site as a top, to a CAS structure, without starting from scratch. I've got 2 separate hierarchy's in my LAB (One CAS with a Primary, and one Primary StandAlone), but i can't really seem to find out how this can be done. Is it just me thats looking in the wrong places, or have i miss-understood what they mean by this? Hope you all have a great christmas Best regards Eirik // Xandor