Site codes and migration from 2007 R3 to 2012 R2

Hi,
We have SCCM 2007 R3 in our environment with one standalone primary server in our main office, secondary server in an off site location and another distribution point in another location. My question is, If I build a 2012 R2 server and prepare it on a VM,
can I put the same site code on it or does it need to be different?
Basically, I would like them to run side-by-side and migrate slowly but surely or am I going about it the correct way?
Thanks,
Niall
Niall Carter

Agree with Jason, you need to use new site code.
For SCCM migration side by side, you can refer below link
http://scug.be/nico/2011/08/03/migrate-form-sccm-2007-to-sccm-2012-part-1/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Similar Messages

How to force site code discovery on all the clients, Migration SCCM 2007 to SCCM 2012

HI,
I migrated SCCM 2007 to SCCM 2012 SP1, but the clients does not update the New Site Code Automatically, if I click on Discovery option the client find the new site, but I need do this automatically because are too many clients.
This registry key does not exist on client computers.
HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignmentCode
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryInterval(Min)
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryDuration(Hour)
Any Help?
Thanks.

Hello ICH-CR,
Thanks for writing to the SysCtr ConfigMgr forums.
I think there are multiple solutions to this issue and you can choose whatever fits best to your scenario.
1. While upgrading the clients from SCCM 2007 to 2012 you can assign the clients to your ConfigMgr 2012 site.
http://technet.microsoft.com/en-us/library/gg682060.aspx#BKMK_AutomaticAssignment
You just need to ensure that you have a boundary group and boundaries. More details on
http://technet.microsoft.com/en-us/library/13694ac5-8f3b-42a9-8040-b23f21c79637#BMBK_CreateBoundaryGrp
I would suggest the first method because if you create another child site, you shouldn't have to reassign the clients back again. If that is unlikely then use the following script which is method no 2
2.
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327
This is a VBSCRIPT and can be ran from a network location using the PSEXC
3. Here is a smaller script
'Replace with your Site Code sSiteCode = "EnterNewSiteCode"
sMachine
= "."
set oCCMNamespace
= GetObject("winmgmts://"
& sMachine & "/root/ccm")
Set oInstance
= oCCMNamespace.Get("SMS_Client")
set oParams
= oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
oParams.sSiteCode
= sSiteCode
oCCMNamespace.ExecMethod
"SMS_Client",
"SetAssignedSite",
oParams
You can use this script as a logon script .
Anurag
Microsoft Certified Professional| Microsoft Certified Technology Specialist (ConfigMgr)
This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights.
My Blog
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Fatal Error: Could not find Feature AnalyticsLinks in sharepoint 2010 while migration from 2007 site using stsadm command

Fatal Error: Could not find Feature AnalyticsLinks in sharepoint 2010 while migration from 2007 site using stsadm command

Hi ,
Firstly, I need to verify the followings:
Whether you created a feature called AnalyticsLinks and activatated it at SharePoint 2007 site.
Whether you installed the feature at SharePoint 2010 site.
Please deactivate the feature AnalyticsLinks, then migrate SharePoint 2007 site to SharePoint 2010, compare the result.
Also , please check whether you have installed the feature AnalyticsLinks at your SharePoint 2010 site. If not, please install and activate it, compare the result.
Here are some similar posts for you to take a look at:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/17b17bd3-126c-44d4-bd58-38dd613017a0/fatal-error-could-not-find-feature-reviewpublishingspd1055?forum=sharepointadminprevious
http://mrin17.wordpress.com/2009/09/15/fatalerror-could-not-find-feature-s2siteadmin-while-importing-sites-from-different-server-at-sharepoint/
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Migration from 2007 and Archive Mailbox PST import question

Our enterprise will be migrating from Exchange 2007 SP3 to Exchange 2013 CU3 very shortly. Exchange 2013 is set up and I am in coexistance mode currently. Everything is working fine with the legacy redirection, I have tested some mailbox migrations and they
work fine. We currently use Mimosa Nearpoint as a third party email archive product.
As part of this migration from 2007 to 2013, we plan on moving away from Mimosa Nearpoint and utilizing the Exchange 2013 Archive Mailbox feature. We will give each user an Archive Mailbox. We have the ability to export the users existing archive out of
NearPoint to .PST files and then migrating them directly into the users Archive Mailbox using the "New-MailboxImportRequest -IsArchive" powershell commandlet. This has been tested and works fine with one very important exception.
When I export from Nearpoint, I have to export the entire contents of the archive, I cannot set date ranges. So when I do an export, it also contains the contents of the user's mailbox. I have managed folder policies in place in the Exchange 2007 environment
which delete all contents of the mailbox older than 60 days, but when I import the .PST to the archive, it imports ALL items into the Archive Mailbox. So I have 60 days worth duplication of items.
It is my understanding that if I imported the Archive .PST directly into the users production mailbox in the 2013 side, that it would not import duplicate items. I am trying to find out if there is any process which will do the same thing with me importing
directly into the users Archive Mailbox.
Thanks you,

Hi,
We used a third patry email archive product to export to .pst files, so it is too hard to say that whether it cause this issue.
However, I found a method to delete the duplicate items from our mailbox via MFCMAPI Tool.
Please make sure that the Exchange Server mailbox has been backed up first.
Details in the following KB:
How to remove duplicate folders in Outlook when connected to an Exchange Server mailbox
http://support.microsoft.com/kb/2509983
I also found a script to remove duplicate items.
This script will scan each folder of a given mailbox and removes duplicate items from those folders. You can specify how the items should be deleted and what items to process, e.g. mail items or appointments. Sample usage is after a misbehaving synchronization
tool creates duplicate items or (accidental) import of PST file with duplicate items.
*****Please also make a full back up first*****
Removing Duplicate Items from a Mailbox
http://gallery.technet.microsoft.com/office/Removing-Duplicate-Items-f706e1cc#content
Disclaimer
The sample scripts are not supported under any Microsoft standard support program or service.
The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose.
The entire risk arising out of the use or performance of the sample scripts and documentation remains with you.
In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss
of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Driver and Driver Package migration from 2007 to 2012 R2 query

Dear Team,
I am in the process of migrating the drivers and DriverPackage from SCCM2007 to CM2012 . I am following the below steps and also i am getting below warning message while doing Driver migration.
1) Copied all the driver source path from SCCM2007 to 2012 folders and shared the same.
2) By using migration Utility , i have migrated all the drivers from 2007 to 2012 .
3) After the migration i have changed the dirver source path at CM2012 side pointing to new CM12 driver source path.
4) I have started the DriverPackage migration.
5) After the DriverPackage migration , i have changed to DriverPackage Source path at CM12 side pointing to new CM12 dirverpackage source.
Please help me my steps and procedure and suggest if anything i need to do extra .....
My question and observation :
1) During the driver migration , i got a warning message like . Some drivers not able to migrate due to unsupported by CM2012 .
    a) Is there any way i can find unsupported model drivers before or after the migration
    b) Is there any other process to migrate Unsupported drivers from 2007 to 2012 other than manual import or script basis
2) After the DriverPackage migration and after the change in the DriverPackage source path. I am not seeing any folder creating in DriverPackage new source path (I understood the reason).
   a) Is there any way i can recreate those folders in new source path after the DriverPackage Migration ?
   b) What is the best process for the DriverPacakge migration from 2007 to 2012 regarding the SourcePath.
Thanks in advance....
Raja

A good article written by Johan Arwidmark
http://www.deploymentresearch.com/Research/tabid/62/EntryId/71/Migrating-unsupported-driver-packages-from-ConfigMgr-2007-to-supported-packages-in-ConfigMgr-2012.aspx
Benoit Lecours | Blog: System Center Dudes

Issue with Excel Access Web Part, with sites that were migrated from 2010 SP to 2013 SP

Hello,
If I try to add an Excel Access Web Part to a page I get the following:
**Note: This only happens with sites that were migrated from 2010 SharePoint to SharePoint 2013. If I create a new site the feature works like it should and loads the workbook. I've tested this on several sites, our environment is enterprise as well. Being
that the majority of our sites were migrated from 2010, I need this to work!

Can you try below fix and let me know
http://blogs.technet.com/b/excel_services__powerpivot_for_sharepoint_support_blog/archive/2013/05/21/excel-services-the-workbook-cannot-be-opened.aspx

Migration from 2007.1 to 10

Hi,
Does anyone know if migration from 2007.1 to ATG 10 needs to step up to ATG 9 first? That's a logical step but in my Migration Kit, I found DB scripts that takes your schema from 2007.1 to 10.
Does anyone know where the ATG 2007.1 to ATG 9 migration document can be found? The link is broken on the old communities site.
Andrew

Here is the link to a page where you will find the portalconsistencychecker.ZIP file.
"https://codesamples.projects.dev2dev.bea.com/servlets/Scarab/remcurreport/true/template/ViewIssue.vm/id/S69/eventsubmit_dosetissueview/foo/resultpos/-1/nbrresults/0/action/ViewIssue/tab/4/readonly/false"
Regards
Sagar

Some clients migrated from 2007 is presented with the self signed certificate in 2013

I have migrated from 2007 to 2013. I did a couple of test migrations and on the ones with domain member computers Outlook is giving a certificate warning. The certificate they are presented with is the default self signed certificate on the 2013 server.
Even though I have added a trusted public certificate to Exchange and checked of to use With IIS.
I see that the default certificate is also checked of to use With IIS and it cant be removed in ECS. Shouldnt this be removed from IIS all together when adding a New certificate? And why does some Clients gets presented With the self signed and some With
the Public? For instance owa is presented With the Public cert. Also and Outlook I tested from outside the domain.
Regards

Only the UCC certificate should be bound to IIS.
Are any clients using POP or IMAP, which also use SMTP? In this case clients can be presented with the "wrong" certificate as well.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Upgrade Call Manager from 8.5(1) to 10.5(1) and migrate from MCS to UCS...

We are upgrading UCM from 8.5(1) to 10.5(1) and migrating from MCS to UCS. We used UCM 8.5 OVA (7500 user) and migrated to UCS.
Once migrated to UCS we upgraded UCM to 10.5(1). We wanted to use OVA to accommodate 10,000 users, hence took backup of 10.5(1) cluster and installed new servers with new 10.5(1) OVA (10,000 users).
While doing DRS restore, system we were not able to perform a restore. It seems UCM is not recognizing the XML file. It is strange as we took the back from UCM 10.5(1) and trying to restore same version, only difference is upgrade was done with 7500 user OVA and we are now trying to install 10,000 user OVA.
Has anyone run into similar issue? any help will be great.
Thank You.

This thread is 5 months old but doesn't seem resolved...
I ran into this same scenario last week. Was using the same SFTP server for backups and restores during migration from 7.1(5) to 10.5 and during final rebuild/restore of the "to-be" production 10.5 Publisher, the DRS server was unresponsive and blamed the Master Agent or SFTP server. I had restarted Master and Local agent repeatedly, and regenerated ipsec certs to no avail.
TAC suggested I try a different SFTP server (which I already had, with the same files), and try deleting the .xml files that were included with the backup (drfComponent.xml and processhost.xml). I installed TitanFTP, per TAC's recommendation, deleted the processhost.xml file, regenerated the ipsec certificate one last time, restarted DRF Master, and then DRF Agent, and was able to start a DRS Restore.
Try the above process if you're still having issues.

ACS4 installation and migration from ACS3

Question: Has anyone installed ASC4 and migrate from ACS3? Any problems, concerns?
The installation of ASC4 would happen on the same server as the current ASC3 correct?
Since you will need to restart the JBOSS etc for configuration changes. This means that ASCS3 could suffer some downtime?

See,
to read how we performed the upgrade and see some issues:
http://www.oracle.com/technology/products/forms/index.html
http://www.oracle.com/technology/products/forms/htdocs/upgrade/index.html
http://www.oratransplant.nl/category/oracle/forms/6i-to-10g-upgrade/
Good Luck!!

POST MIGRATION - Project Site cannot be found after migration from 2007 to 2010

Hi,
I have done full migration from Project Server 2007 to Project server 2010. All the databases have been restored. The details in the Project Center are coming correctly. But When I open the Project Site , I get error webpage cannot be
found.
I have done the Bulk update but it is not updating the URL to 2010 URL.
Please help.
Regards

Use PowerShell to list all the sites in your PWA site collection.
There are many examples online.. Here is a link that is useful
http://blogs.msdn.com/b/vijay/archive/2009/10/01/how-to-list-all-the-sub-sites-and-the-site-collections-within-a-sharepoint-web-application-using-windows-powershell.aspx
Cheers
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

Inter-site replication and KCC, when migrating from 2008 SP1 to 2012 R2

Hello,
We have a very simple AD infrastructure, two sites. I have built out a 2012 R2 server, extended the AD schema and promoted it to a domain controller. Reviewing the existing AD replication topology, we currently have a 2008 SP1 server as a DC
designated as the source/destination for inter-site replication, which appears to have been decided by KCC.
I will be decomming this 2008 SP1 server, having migrated off the FSMO roles to a few other DCs.
Will KCC automatically know to adjust the replication topology when the 2008 SP1 DC is offline? Should I demote it after migrating off the FSMO roles?
Thanks,
Matt

Hi,
Thanks for your post.
By default, the KCC reviews and makes modifications to the Active Directory replication topology every 15 minutes to ensure propagation of data, either directly or transitively, by creating and deleting connection objects as needed. The KCC recognizes
changes that occur in the environment and ensures that domain controllers are not orphaned in the replication topology.
For more detail information, you could refer to:
http://technet.microsoft.com/en-us/library/cc961781.aspx
For the migration, you could transfer the Flexible Single Master Operations (FSMO) Role and remove the Windows 2008 R2 domain controller, please refer to:
Step-By-Step: Active Directory Migration from Windows Server 2008 R2 to Windows Server 2012 R2
http://blogs.technet.com/b/canitpro/archive/2014/05/28/step-by-step-active-directory-migration-from-windows-server-2008-r2-to-windows-server-2012.aspx
Regards.
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 Support, contact [email protected]

Resources and public folder database - migration from 2007 to 2013

We migrated our resource mailboxes thru the move mailboxes in 2013 EAC but now we're at the point of decommissioning our 2007 servers. Before the actual decommission we stopped all 2007 services and dismounted all 2007 databases. Once we did
this the resources would no longer work - errors pertaining to cannot directly book the resource.
I had to bring up the public folder database for the moved resources to work again. We do not use public folders any longer so we did not do any type of public folder migration. Do I need to do this for the resources to work?

Hi,
Could you please tell me your Outlook version?
I saw someone got the following error when he tried to book resource after migrating from Exchange 2007 to Exchange 2010, if Outlook version is Outlook 2007. But Outlook 2010 worked well.
"Cannot directly book a resource for this meeting."
Please switch between online and cached mode to check the result. And please check if this issue occurs in OWA.
If possible, please use Outlook 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migration from 2007 to Latest version

Hi,
We have a developed site in SharePoint 2007 with custom Webparts and also with existing features. Now we want to upgrade this site to latest version. Do we need to follow any specific steps for upgrade because of having Custom webparts? Please provide the
steps how to upgrade from 2007 to higher version.
Thanks,

Take a look at the following sites. They provide guidance on the upgrade process. Please Note that without a third party product you will need to first upgrade to SharePoint 2010 and then from there to 2013. And yes, you will need to make
sure that all custom code migrations are installed on the new farm. The code may also need to be re-factored to work in 2013. Its mostly backwards compatible, but there is no guarantee.
Upgrade from SharePoint 2010 to 2013 - http://technet.microsoft.com/en-us/library/cc303420(v=office.15).aspx
Upgrade from SharePoint 2007 to 2010 - http://www.microsoft.com/en-us/download/details.aspx?id=3837
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Site codes and migration from 2007 R3 to 2012 R2

Similar Messages

Maybe you are looking for