Upgrade OS of Primary Site (2008 R2 to 2012 R2)

Our org has a single primary site (SCCM 2012 R2 5.00.7958.1203) and is comprised of two site systems/servers and roughly 2500 clients.
Site System/Server 1 has the following site system roles installed:
Distribution Point
Management Point
Software Update Point
Site System/Server 2 has the following site system roles installed:
Site Database Server
Reporting Services Point
Both servers are currently running Windows Server 2008 R2. We'd like to upgrade the OS of these two site systems/servers to Windows Server 2012 R2 but as I understand it, Microsoft does not support this as an in place upgrade (Infrastructure
Upgrade for Configuration Manager).
Also, while it is not absolutely necessary, it would be nice to rename the site systems/servers in the process in order to better conform to our organization's naming conventions.
What is the best process to accomplish this without any downtime to existing clients? I was thinking something along these lines...
Build out a 2nd site/servers with Windows Server 2012 R2 and the correct server names running side-by-side with the current production SCCM site/servers.
Grant the new site's MP computer account permission to modify the System Management container in Active Directory. Will this have any impact on the production environment and existing clients?
Re-install the clients from the new site that is running 2012 R2 OS.
Decommission the old site that is running on 2008 R2 OS.

Grant the new site's MP computer account permission to modify the System Management container in Active Directory. Will this have any impact on the production environment and existing clients?
That will allow the new site to write information to the AD, if configured. That will only have an impact when you've got an overlap in the configured boundaries and you're using site assignment boundaries in combination with auto site assignment
of clients.
Also, if there is anything in the old environment that you would need in the new environment you can look at migrating those objects. See for more information:
http://technet.microsoft.com/en-us/library/gg682006.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

Effect on OSD if remove primary site from SCCM heirarchy

Wanna ask, just a theory question, im currently planning to decommission and upgrade my current primary site server. The process will take roughly a few days. At the same time, I also have other site system server that also acts as an MP (has MP role). So,
for the time being I would not have an active primary site for a couple of days.
Question is, during that timeframe (when primary site not available), am I able to still do OSD? Was thinking the only issue of not having a primary site at that time, my user client machine will not be able to get the latest policy
cause any new policy will be push down from the primary site right...but the client will only be able to get the old TS advertisement correct... Question as below
Does the client machine still able to run the old advert advertised to it?
Does the client machine cache the TS advert and store it locally on their machine?
All the OSD content (boot image, OS image etc) is available in the DP, so it should be able to PXE boot and execute the TS correct if the primary site is not available?
Read the net on PXE boot flow at
http://blogs.technet.com/b/pingpawan/archive/2014/01/12/deep-dive-pxe-boot-flow-for-sccm-2007-2012.aspx. Its says as below. What I don't understand is isn't the primary server is the only one that can access the DB? Don't quite get it when it says
WDS can also access the DB....?
WDS/PXE sever runs a stored procedure, LOOKUPDEVICE for the client machine against SCCM DB. If the machine is found in the DB or If there is an advert for Unknown collection, WDS signals client to proceed with the PXE
boot.

Which roles are installed on the site server?
Torsten Meringer | http://www.mssccmfaq.de
Roles installed on my primary site is
Management point
SUP
Site System
Component Server
Site Server

Upgrading domain from 2008 R2 to 2012 R2

I am looking to upgrade my domain from server 2008 R2 to 2012 R2. We have 10 remote sites, each with a single physical ESXi host hosting 2 vms, 1 2008 R2 vm with the ADDS/DHCP/DNS/File Services (user home drives) roles and the second 2008 R2 vm
runs WDS/MDT and a couple applications. At our main site we have a physical 2008 R2 DC which holds all the FSMO roles, a vm with the ADDS/DHCP/DNS/File Services roles, and another vm running WDS/MDT.
I've gathered from my research that Microsoft recommends clean installs when upgrading DCs but since our DCs are also file servers that's not an ideal course of action for us, it'd be a lot of additional steps. My plan at this point
is to bring up a new physical 2012 R2 server, make it a DC, transfer the FSMO roles to it, then demote and retire the current physical 2008 R2 server. For the virtual DCs, since they are also file servers, I'm leaning towards in-place upgrades
on them, unless anyone would advise against.
The other thing I'm considering is creating a 2012 R2 DC at each remote site, then demoting the current 2008 R2 DC, leaving some combination of DHCP/File Services on it, then run an in-place on it to 2012 R2. This would requre another Windows license
though since our physical hosts are not on Hyper-v.
For the virtual servers running WDS/MDT, I personally prefer an in-place so I don't have to move the MDT deployment share, but I'm open to suggestions.
What are your recommendations? Which server should I upgrade first? How much time should I allow between each DC upgrade? I appreciate the help.

As per recommendations, A DC should be solely utilized for AD/DNS/GC & if environment is small for DHCP. The problem in using DC for other purpose arise during upgrade scenario, when you have to demote the DC or performance. Demoting the DC is very simple,
but if its running with additional role, it becomes challenging, if demotion has to be performed forcefully.
Secondly, from the security point, its not a great idea to run DC with other roles esp file servers, if there is any infected file then the whole domain can be compromised or infected.
What is more relevant in upgrade is testing the applications before you perform or upgrade the schema. If there is no issues then you can perform the upgrade based on your convenience. But necessary documentation & testing prior & post has to be
followed.
My personal recommendation would be upgrade the schema(surely test the schema upgrade in lab before you do in production), create a new server either VM or physical, configure it as an DC & transfer all FSMO role & slowly try to segregation between
DC & non DC servers.
Yes, i know it will cost additional licensing burden, but from the environment point of view it will provide you an ease of administration & troubleshooting.
http://blogs.technet.com/b/chrisavis/archive/2013/10/01/performing-an-in-place-upgrade-of-server-2008-r2-to-server-2012-r2.aspx
http://blogs.technet.com/b/canitpro/archive/2013/06/18/step-by-step-active-directory-migration-from-windows-server-2008-r2-to-windows-server-2012.aspx
Awinish Vishwakarma - MVP
My Blog: awinish.wordpress.com
Disclaimer This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Want to upgrade 2008 R2 to 2012. Upgrade advisor giving errors relating to Database Compatability Level and Server Collation

I want to upgrade a SQL Server from 2008 R2 to 2012. When I run upgrade advisor, I get the following error messages:
Rule "Valid Database compatibility level and successful connection" failed.
The report server database is not a supported compatibility level or a connection cannot be established. Use Reporting Services Configuration Manager to verify the report server configuration and SQL Server management tools to verify the compatibility
level.
Rule "Valid Database server collation and successful connection" failed.
The SQL Server Database Engine is not configured with a valid server collation and cannot be used as the Reporting Services SharePoint Shared Service catalog database.
The database called ReportServer has Collation = Latin1_General_Cl_AS_KS_WS and Compatibility level = 100

Hi Andrew,
Regarding to the first error message, please check the Reporting Service Configuration Manager, make sure that you connect to ReportServer database from the correct server
and use servername\instancename format connection string. For more details, please review this similar
thread.
Regarding to the second error, it is caused by that the current SQL Server Database Engine server is using an incompatible server collation.
SQL Server 2012 Reporting Services SharePoint mode utilizes the SharePoint shared services architecture. SharePoint does not support SQL Server Database Engine configured for case sensitive or server collations or binary server collations.
And since the SQL Server Database Engine server collation property cannot be changed, you will not be able to complete an upgrade of Reporting Services. You will need to migrate your Reporting Services installation to a new server which is using a compatible
server collation. For more details, please review the following article:
Incompatible Database Engine Server Collation:
https://msdn.microsoft.com/en-us/library/hh759335%28v=sql.110%29.aspx?f=255&MSPPError=-2147217396
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Upgrading hyper-v 2008 r2 to 2012?

is it possible/will it be possible to just upgrade hyper-v server from 2008 r2 to 2012 or will I have to reinstall the whole os and vms?

"Hyper-V Server (Server Core) cannot be upgraded to Hyper-V Server 2012. You can choose to install
a new copy of Hyper-V Server 2012 instead, but this is different from an upgrade, and does not keep your files, settings, and programs."
Any know how to work around this problem?
Yes - export your VM's and re-install your host OS! It really doesn't add that much time.
And here's a tip for quicker exports - if you have a VM that has several really large VHD's you can temporarily remove the VHD's from the guest VM config and then export. I had an SBS 2011 VM with the Guest OS, Exchange, Swap and User data all on separate
VHD's.
I shut down the VM normally and then detached the large user data VHD's. The export/import of the VM went much faster. Once the Host OS was re-installed and the VM was re-imported, I just re-attched the user data VHD's before restarting the VM
and the server in the VM was none the wiser. I went through the trouble of keeping the VHDs in same location in the virtual SCSI controller in the guest VM configuration settings, but I don't know if that's strictly required or not. It worked like
a champ and didn't add that much time to the overall process of rebuilding the HyperV host OS. If I ever get comfortable enough to switch to Server 2012 HyperV, I'll do the exact same process. For something as simple as a hypervisor OS install,
upgrading it doesn't make much sense to me! As others have pointed out you are MUCH better off doing a clean install. Especially if it won't upgrade it for you :o)

Client Upgrade on Primary Site Server

This should be an easy question but I really want confirmation.
When you perform a Cumulative Update does the Update upgrade the client also on your primary site server? If so do when you create a device collection for x86/x64 clients do you exclude the site server from getting push?

Hi,
No the SCCM Client stays at version 5.00.7958.1000 on the primary site.
If you wanted you could upgrade the SCCM client on the primary manually by running.
C:\Program Files\Microsoft Configuration Manager\hotfix\KB2970177\Client\x64\configmgr2012ac-r2-kb2970177-x64.msp and then exclude it from the below collection or let it go out automatically.
This is from an older version but the principle is still the same.
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
You can go straight from R2 to CU2. You do not need to install CU1 first.

Issue getting WDS to Install for PXE in SCCM 2012 SP1 Primary Site

Hi All
I'm trying to get PXE boot working from our SCCM 2012 box but it never actually gets to the point of installing WDS when I check the box for PXE booting. I don't have SMSPXE.log since it never gets to that point and the distmgr.log never reaches
that point either. I've tried
uncheck pxe boot option - restart - re-check
uncheck pxe-boot - restart - install wds - leave it unconfigured - reboot - check pxe boot
uncheck pxe-boot - uninstall the vcredist 2008 packages - rebooting - install vcredist - check pxe boot option
the above with installing wds unconfigured
Below is the relevant portions of the distmgr.log file after I enable the pxe boot option no matter what manner of software is installed. We are running it on a VM in a Hyper-V 2012 enviornment in Windows 2008 SP2 x64. This issue is similar to this link
WDS PXE Secondary Site Issues but mine is on the Primary Site.
ConfigureDP SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:09 AM 4008 (0x0FA8)
DP registry settings have been successfully updated on TUSC2012.TALISKERUTAH.LOCAL SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
STATMSG: ID=9500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TUSC2012.TALISKERUTAH.LOCAL SITE=001 PID=2728 TID=4008 GMTDATE=Thu Mar 28 17:48:10.083 2013 ISTR0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
STATMSG: ID=9503 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TUSC2012.TALISKERUTAH.LOCAL SITE=001 PID=2728 TID=4008 GMTDATE=Thu Mar 28 17:48:10.084 2013 ISTR0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\TUSC2012.TALISKERUTAH.LOCAL\"]MSWNET:["SMS_SITE=001"]\\TUSC2012.TALISKERUTAH.LOCAL\" SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
ConfigurePXE SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
CcmInstallPXE SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, PxeInstalled SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
Running: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
Waiting for the completion of: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:10 AM 4008 (0x0FA8)
Run completed for: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Created the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
GetFileAttributesW failed for SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
FindWimgapiDll failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Running: msiexec.exe /quiet /i c:\program files\microsoft configuration manager\wim\wimgapi.msi /log c:\program files\microsoft configuration manager\wim\wimgapi.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Waiting for the completion of: msiexec.exe /quiet /i c:\program files\microsoft configuration manager\wim\wimgapi.msi /log c:\program files\microsoft configuration manager\wim\wimgapi.log SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:14 AM 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:29 AM 4668 (0x123C)
Created policy provider trigger for ID 16777217 SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:29 AM 4656 (0x1230)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:34 AM 4668 (0x123C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 3/28/2013 11:48:39 AM 4668 (0x123C)

HI again, sorry for the late reply.
By saying that WDS don't get configured, I mean that when i enabled the PXE functionality, the WDS role got installed but the folder remote install wasn't created.
I ahve now actually gone back to an earlier snapshot from before I started play with the PXE settings of the VM and now nothing happens when activating PXE on the distribution point, but not even the smspxe.log is created.
The Account used is a local admin and the distribution point is located on the primary site server.
EDIT: in the events log, it states the following:SMS_SITE_COMPONENT_MANAGER on computer XXX.XXXX.XXX reported: SIte comoponent Manger failed to to install on this site system.
On error (source: MsiInstaller) below:
Product Application Web Service -- Internal Error 25001. 80070490
I havent mentioned it earlier, but the Server OS is Server 2012.
I hope this might help you help me :)

Upgrade from SQL server developer 2008 R2 to SQL Server developer 2012

Hi,
We have bought 5 licenses of SQL server developer 2012.
This licenses provided us an option to use SQL server 2008 R2. And we have been using 2008 R2 till now.
But now we want to upgrade to SQL server developer 2012 edition
I want to know the process for up-gradation. When I looked at the licensing portal, it says "This product does not require a product key"
My questions are:
1) Should I download the 2012 version from licensing center and pass the downloaded copy to respective team members?
2) Can the team member download the SQL server 2012 developer edition from Microsoft site and install it on their machines?
3) Do we need to first un-install 2008 R2?
4) How the licensing can be managed in cases of products which say "This product does not require a product key.", i.e. how can I make sure that no more than 5 installations are done by the team
Thanks

Hi,
We have bought 5 licenses of SQL server developer 2012.
This licenses provided us an option to use SQL server 2008 R2. And we have been using 2008 R2 till now.
But now we want to upgrade to SQL server developer 2012 edition
I want to know the process for up-gradation. When I looked at the licensing portal, it says "This product does not require a product key"
My questions are:
1) Should I download the 2012 version from licensing center and pass the downloaded copy to respective team members?
2) Can the team member download the SQL server 2012 developer edition from Microsoft site and install it on their machines?
3) Do we need to first un-install 2008 R2?
4) How the licensing can be managed in cases of products which say "This product does not require a product key.", i.e. how can I make sure that no more than 5 installations are done by the team
Thanks
1. Developer edition has license associated with it .And yes you can download it if you have subscription.But please be informed that you cannot use Developer edition in production,its not allowed and illegal.
2.You can upgarde from SQL server 2008 R2 to 2012 developer edition by Inplace upgrade method ,you can also follow side by side approach.For side by side approach you have to get new box ,intall OS,then install SQL server 2012 ,move logins and jobs and move
databases by backup restore.You must see supported upgrades
http://technet.microsoft.com/en-us/library/ms143393(v=sql.110).aspx
3.No not ins any case ,please dont do that
4.Licensing question should best be asked with Microsoft licensing expert.
reg process of upgarde first run upgrade advisor and look for error if any.Then run SQL server 2012 setup and in maintenance section select edition upgrade,other process is same as SQL Server installtion
http://www.mssqltips.com/sqlservertip/2505/version-and-edition-upgrades-with-sql-server-2008-r2/
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Replacing the primary site server, SCCM 2012 R2

Hi,
Setup is currently SCCM 2012 R2 with the primary site server on Windows 2008 R2 on a Hyper-V VM with a separate physical SQL server on 2008 R2 (Windows and SQL). I'm not making any changes to the SQL server at this stage.
I want to completely replace the primary site server VM completely with a brand new VM using Windows 2012 R2.
I was looking to run the SCCM setup and using the Expand an existing stand-alone primary into a hierarchy option but it wont let me do that due to "The site code you specified should not be the same as the primary site's site code".
So seems this Expand an existing option isn't the right option for me?
Do I just add the new server in the SCCM console and add all roles and test and then delete the roles from the old server?
Thanks
EDIT: I have 7 Secondary sites, so I dont want to just start over by doing some sort of backup and restore to the new server unless someone can tell me that wont break my hierarchy.

a backup and recovery is the correct way to do this, but there are a few things you should keep in mind.
Do a backup of your current environment and shut everything down.
install new vm, ensure the configuration is identical, (dns, hostname, etc...); install the same software and pre-requisites,
do a recovery
check the following links on how to do a backup and restore:
http://www.windows-noob.com/forums/index.php?/topic/7403-how-can-i-backup-system-center-2012-configuration-manager/
and
http://technet.microsoft.com/en-us/library/gg712697.aspx

Move SUP role from Server 2008 R2 to new Site System running Server 2012 R2

Is it possible to move the primary SUP role which is currently running on a separate site system under Server 2008 R2 (WSUS 3.0 SP2) and move it to a new site system running Server 2012 R2 using the same SUSDB? I've moved the SUP role
around before by setting up a secondary SUP (using the same DB) then removing the primary SUP role which causes the secondary SUP to become the Primary but that was using the same version of OS and WSUS. With the version of WSUS being different
on Server 2012 R2, I was thinking this may not be possible since the documentation says the WSUS versions must be the same when creating multiple SUP roles.

Hi,
>>I was thinking this may not be possible since the documentation says the WSUS versions must be the same when creating multiple SUP roles.
As the document indicated, "When you have multiple software update points at a site, ensure that they are all running the same version of WSUS." So the scenario you decribed should be not supported.
Reference:Prerequisites for Software Updates in Configuration Manager
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

I did an Unsupported InPlace OS Upgrade from 2008-R2 to 2012-R2

Well, I misunderstood what was supported and upgraded the OS on a SCCM 2012-R2 server from 2008-R2 to 2012-R2. (The one and only SCCM-server in the site)
All seems to work well, my concern now is what can I expect of future problems? Should I do the backup-install-restore procedure now to be sure or let it run until... "maybe something" happens?
Thanks.

"not supported" just means that MS did not test that scenario (and it does not automatically mean that it does not work).
I've done such an OS upgrade in my lab and were running into some smaller issues (MP/DP/SUP = the roles that require IIS) and were able to fix them by removing and re-adding those roles but YMMV.
The supported way would be: recover from backup. But you can also have a close look at all roles and see if they are still working.
Torsten Meringer | http://www.mssccmfaq.de

I upgraded to Mavericks and my 2008 iMac is slower than slow.

I have a 2008 IMac with 2GB Ram and 320GB HD. I have been upgrading through out and up to Mountain Lion never had any issues with the new OS systems. I upgraded to Mavericks about 2 months ago and the system continues to get slower and slower to where I really do not want to use it any longer. I spoke to someone at apple and they said from all of the upgrades there are programs taking up overhead that no longer are needed. If I bring the computer in they can help resolve the issue. The Apple store is about an hour drive from where I live. Seems to me that there must be an easy fix. I am not that computer literater and switched from Windows to Apple because of the reputation. Now all I do is watch that colored pinwheel on my screen more than anything else. Does anyone have a simple suggestion or do I need to take it to Apple and have to pay them to fix what they have caused.

RAM is pretty cheap these days. It will depend on the exact model of iMac you have. Just for a rough idea I took a look here Computer memory upgrades for Apple iMac (Early 2008) Desktop/PC from Crucial.com and found a 2 x 2GB upgrade kit for $72.
Most of the sites that sell RAM have instructional videos you can watch so you can get an idea of how difficult the installation might be for you. I've installed RAM on my MacBook Pro and it was not very difficult, and the iMac installation looks easier than that. But that would depend on your own comfort level with doing it. I've done a lot of this sort of installation over the years on my Macs so I'm very comfortable. But you do have to be careful, as the innards of a Mac can be very sensitive to static electricity, and it is possible to damage components if you don't follow directions carefully. But I would see if there are software issues that can be addressed first before you go investing in more RAM.

Problems using SQL Server 2014 upgrade advisor on a windows 2008 sp2 server

I got sql server 2014 upgrade advisor up and running on a windows 2012 vm and every thing works fine, but I am having trouble installing it locally for a SSRS Box. The SSRS box is running windows 2008 sp2 enterprise edition, but when I try
and run the SQLUA.msi install nothing happens.
anyone else experience this issue?

Hi jesse,
Welcome to the forum :-)
Can you please clarify your issue in more details. I did not understand what you are doing. What do you mean by "installing it locally for a SSRS Box". Do you mean that you are trying a simple installation which do not work, and raise an error?
If so then (1) we dont need the extra information about "why you need the SQL Server" :-) we just need to help you install it regardless the SSRS. (2) We do need the full error log and the error message that you get.
By the way, The SQLUA.msi is just a small utilities named "Upgrade Advisor"
http://msdn.microsoft.com/en-us/library/ms144256.aspx
Do you want to install the SQL Server itself?
What is your current SQL Server on the local windows 2008 server?
[Personal Site] [Blog] [Facebook]

CCMSETUP not updating on SCCM 2012 SP1 CU3/CU4 primary site

I have a SCCM 2012 SP1 CU3 primary site and i can't upgrade the local installed SCCM Client.
The error I get in ccmsetup.log is:
<![LOG[MSI: Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002]LOG]!><time="15:44:22.408-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:300">
<![LOG[MSI: Action 15:44:22: Rollback. Rolling back action:]LOG]!><time="15:44:22.562-60" date="02-08-2014" component="ccmsetup" context="" type="0" thread="2496" file="msiutil.cpp:314">
<![LOG[File C:\windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterHostingConfiguration.
ErrorMessages:
Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002
]LOG]!><time="15:45:00.798-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:872">
<![LOG[Client installation has failed too many times. Ccmsetup will now abort.]LOG]!><time="15:45:00.830-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7941">
<![LOG[Successfully deleted the ccmsetup service]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2496" file="ccmsetup.cpp:3320">
<![LOG[InstallFromManifest failed 0x80070643]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7086">
<![LOG[CcmSetup failed with error code 0x80070643]LOG]!><time="15:45:05.832-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2324" file="ccmsetup.cpp:10544">
I have this on my primary and secondary servers as well.
Is upgrading to R2 recommended and will that solve this issue ?
When googling to this issue i found that there is a solution for this: remove MP, upgrade Client, install MP.
But this is my primary and secondary and on secondary i am not allowed to remove the MP. It is hardcoded enabled.

Try the following steps to specify the hotfix when installing the client.
1. Open an elevated command prompt.
2. Run a command line similar to the following – if CU3 has already been installed, the MSP file below should be on the site server, in the
\\servername\SMS_SITE\Client\hotfix folder:
\ccmsetup.exe PATCH=\Configmgr2012ac-sp1-kb2882125-x64.msp
Juke Chou
TechNet Community Support

Primary Site Deploy Prerequisite Check Failed

1. Symptom description: check failed
SQL instance when you run the Prerequisite Check SCCM 2012 for a new primary site.
2. Environment: My remote SQL Server 2008 R2 SP1 CU6 and uses
a named instance called INST01 (SRV302 \ INST01). My server will be the primary site watch requirements (SRV501). I
have a VM to test that was used to ratify the SCCM 2012 R2 (vSRV210).This
VM had a primary site that was the basis of data in SRV302 \ INST01, this site has been removed by the Configuration Manager Setup wizard, he correctly remove the database SCCM 2012.
3. The
exact error message: When trying to run the installation of SCCM 2012 server SRV501, filling in as the database and SRV302.domain.com INST01 for instance, it shows the Prerequisite Check Failed one item as:
"Dedicated SQL Server instance: Configuration Manager requires a dedicated SQL Server instance to host excellant site database. You selected the SQL Server instance That site hosts the Configuration Manager
database for another site. Select a different SQL Server instance for this new site to use, or
resolve the conflict by uninstalling The Other excellant site or moving to a different database SQL Server instance. "
In the file ConfigMgrPrereq.log the message is the same:
srv501.domain.com; Dedicated SQL Server instance; Error; Configuration Manager requires a dedicated SQL Server instance to host its site database. You selected a SQL Server instance that hosts the site">"<05/03/2012 10:00:21>
srv501.domain.com; Dedicated SQL Server instance; Error; Configuration Manager requires a dedicated SQL Server instance to host excellant site database. You selected the SQL Server Instance That Hosts the site Configuration
Manager database for another site. Select a different SQL Server instance for this new site to use, or resolves the conflict by uninstalling The Other database excellant site or moving to a different SQL Server instance. "
4. Any
recent relevant configuration change (s): Only completely removed the test site that was with the database in SRV302 \ INST01, rebooted the server and tried to start the installation of the production site using the instance where it was before (no more no
database SCCM it).
5. Tech diagnosis history: Have you tried doing a restart of the server and
the instance of SQL without success. I did a test site to reinstall the test SCCM VM vSRV210, pointing
to the same instance and it works. But the production server 2012 SCCM has to be SRV501. You
can not create a new instance of the database only for the production site.
What can I do to install the SCCM 2012 instance that (SRV302 \ INST01)?
Is there a procedure for cleanup of an instance of SQL for SCCM 2012?
Is there any way to bypass this check in the SQL setup SCCM 2012?
Att. Rodrigo Krug

Hello,
Beware of the solution, after removingthe key
SMS even passed the Prerequisite
Check, but during the installation,
it stopped with the following error:
Can not write CertBootStrap\SMS_SQL_SERVER\ registry
key on server srv.domain.com.
The operating system Reported error
4
ERROR: Failed to write
to registry certificate configurationon server
srv302.domain.com.
ERROR: Failed to create
SQL Server [srv302.domain.com]certificate
remotely.
I had to recreate the keys from the file. Reg
so that the installation was successful.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\CertBootStrap]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\CertBootStrap\SMS_SQL_SERVER]
No values registered.
With that I succeeded in installing the
primary site in that instance
where we had another base before
SCCM 2012.
This was supposed to be your solution?
Att. Rodrigo Krug

Upgrade OS of Primary Site (2008 R2 to 2012 R2)

Similar Messages

Maybe you are looking for