Sharepoint migration from 2003 to office 365

Hi,
I need to migrate from sharePoint 2003 on-prem to office 365. customer has
650 GB of contents in sharepoint and they want all contents to be migrated to office 365. Customer has 145 office 365 E1 licenses. Can someone help me in how to do this, it will be very helpful.

Hi,
Can someone provide an answer for this please..

Similar Messages

Migrate Exchange 2003 to Office 365

Dear all,
We are going to migrate Exchange 2003 to Office 365. Because of the large number of mailboxes and mail databases, we decide to build hybrid to support coexistence during the migration period.
According to "Exchange Server Deployment Assistant" I found that we can build more Exchange 2010 for that requirement
http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-BwAIAAAAQAAAAAEAiFIAAAA~
I just wonder that after deploying the Exchange 2010, can we move directly the mailboxes from Exchange 2003 to Office 365 or we need to move to Exchange 2010 first (as a "buffer") before moving to Office 365
Thanks a lot !!!

Hello,
The main goal of a staged migration is to migrate Exchange on-premises servers when:
1. You have more than 2000 mailboxes.
2. You plan to migrate over a few weeks and months rather than in a single batch.
3. You want to migrate to the Cloud completely and remove your on-premises Exchange deployment.
Hybrid scenarios are useful when you do not want to remove your on-premises deployment. In some cases there is no technical possibility, it is not cost-effective etc. to move a whole organization to Office 365. In these situations you may decide that moving
only some mailboxes to Office 365 is a good option and create a hybrid deployment.
You need to consider all pros and cons, especially when Exchange 2003 has gone out of support lifecycle and then choose the better option for your organization.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Migrate exchange 2003 to office 365 with single singon

Dear All,
We are going to migrate our mail systems from exchange server 2003 to office 365 with single sing-on.
Please advice me the best way and guide line (information) to do it smoothly.
Thanks in advance.

Dear Andres parnova,
Thanks for your information.
I found series of articles in msexchange.org
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/performing-staged-exchange-migration-office-365-exchange-online-part1.html which has very nice and clear information.
But, in the articles the author did not include ADFS configuration and steps.
I would like to know how to configure ADFS and single sing-on.
Thanks
Min

Migration from 2010 to Office 365

I'm stumped on Office 365 Small Business Premium and the migration from 2010.
I thought that migration would be simple but I can't find any tools mentioned in the articles I read. I thought that it was supposed to be a tool found within 365 where you pull the info from the PST you keep on your desktop.
Do I need to uninstall 2010 and only use the 365 web based email. IF I can keep both, do they sync? Does this sync with the mobile app also?
So right now I have both installed and the users setup for 365 (the login accounts), but I don't have any thing else setup because I don't want to lose any data. I want to make sure that I do this right before I go any further.
No I don't have exchange. Every thing is hosted by Network Solutions and we use pop3 to pull the email.

Hi,
some options/suggestions are here:
http://community.office365.com/en-us/f/158/p/230137/714965.aspx?ss=87fa5dc5-cfde-49c9-ab80-294fc73ccb85#714965
http://community.office365.com/en-us/p/helpcenter.aspx?hcs=8b0e9324-aae1-4a96-a035-619cabe78397#ESKU-Admin-Mail
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
OK. I downloaded those files and they didn't do me any good. The one which would run was asking for a central computer, I'm assuming an email server, which we don't use.
We use pop3 through Network Solutions. We have Outlook on each desktop and the folders are local.
I am reading up on some other stuff on migration. I'll let you know how it goes.

Migration from gmail to office 365 mail box.

Recently, I migrated gmail to office 365.
After I migrated to office 365, outlooks mail box size is almost double of gmail mail box.
ex: One of the user had 26gb data in gmail , aft the migration his exchange online mailbox became 46 gb.
any ideas?
Sutha Thavaratnarajah

Both Office 365 and Gmail uses different systems. Sometimes its normal that size of the mailbox to increase after migration. But in this case its too high so I request you to check for Folder named GMAIL
in the user's Mailbox

Error in migrating SharePoint 2010 list fields to Office 365 list [CSOM]

Hi,
I am trying to migrate a SharePoint 2010 list to Office 365. I created a new ListCreationInfo for a new list in O365. But when i am to trying add fields from SP2010 list, its giving me an error after list.update() -
A duplicate field name "fa564e0f-0c70-4ab9-b863-0177e6ddd247" was found.
if (!l.Hidden)
ListCreationInformation creationInfo = new ListCreationInformation();
creationInfo.Title = l.Title;
creationInfo.TemplateType = l.BaseTemplate;
List list = web.Lists.Add(creationInfo);
//Fields in the list
ctxOnPrem.Load(l.Fields);
ctxOnPrem.ExecuteQuery();
foreach (Field f in l.Fields)
list.Fields.AddFieldAsXml(f.SchemaXml, true, AddFieldOptions.DefaultValue); list.Update();
Note- l is the SharePoint 2010 List.

Answer given on StackExchange -
http://sharepoint.stackexchange.com/questions/128875/error-in-migrating-sharepoint-2010-list-fields-to-office-365-list-csom/129015#129015
Thanks,
Thomas

Decommissioning Exchange 2003 after Office 365 Migration

Hello,
My company recently migrated from Exchange 2003 to Office 365 and are working on decommissioning our on-premises Exchange 2003 server. We believe everything is ready to go, however this Microsoft article: http://help.outlook.com/en-us/140/ff959224.aspx#nextsteps has
a big Caution box warning of "unintended consequences" and recommending I contact Microsoft Support:
I've tried my Office 365 support options, but they only tell me that Exchange 2003 is no longer supported and they can't help me, despite the fact that I'm trying to remove it, not maintain it. So
I'm allowed to pay for a new service, but shouldn't expect assistance in safely moving from my old service...
Regardless, they directed me here, so I was hoping someone might be able to advise about what these "unintended consequences" actually are so I can feel fully prepared to decommission.
Thanks in Advance,
Jim

Hi,
After you’ve verified that all e-mail is being routed directly to the cloud-based mailboxes, completed the migration, and no longer need to maintain your on-premises e-mail organization or don’t plan on implementing a single sign-on solution, you can uninstall
Exchange from your servers and remove your on-premises Exchange organization. For more information, see the following:
How to Uninstall Exchange Server 2003
http://technet.microsoft.com/en-us/library/bb125110(EXCHG.65).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

How to migrate Outlook configuration to Office 365

As we plan our migration to Office365/Exchange Online, I am getting asked questions about the user Outlook profiles. We have users that make extensive use of categories, folder views, rules, etc. In addition, we have a custom Outlook toolbar that is part
of our default image. Can anyone tell me if these items get migrated using the standard Office 365 migration wizard? If they don't is there a way to migrate or export/import this information?
Thanks!
Joe

Hi,
According to your description, I want know the configuration of Outlook after migrate Exchange 2010 to Exchange Online.
If I misunderstand your concern, please do not hesitate to let me know.
Mailbox database will be moved to Office 365, also the mailbox content. The Outlook client can use SCP and DNS record get autodiscover service, then connect to Exchange server and auto-configure Outlook profile. However, dumpster content and old message
missing after migrate to Office 365, please refer to below link and work it out:
https://support.microsoft.com/en-us/kb/2603594?wa=wsignin1.0
For POP3 and IMAP account, and they may not remain the copy in Exchange server, we need to import .pst file to Exchange server. For your reference:
https://technet.microsoft.com/en-us/library/hh781035%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
As client side, we can just move .pst file to new computer, then import to Outlook:
https://support.office.com/en-ca/article/Import-Outlook-items-from-an-Outlook-Data-File-pst-431a8e9a-f99f-4d5f-ae48-ded54b3440ac
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Migrating from 2003 domain/forest level to 2008R2 with all DC's at 2008R2 and 2 other Domain External and Forest Trusts

Is there anything that needs to be done or considered when migrating from 2003 domain/forest level to 2008R2 with all DC's at 2008R2 with 2 other 2003 separate Domain incoming
and outgoing Trusts, one Trust that is a Forest Trust and the other is an External Trust? Is there any chance or risks that doing this upgrade will break either one of these Trust relationships? Some of the user accounts with SID history have been migrated
from both Domain Trusts to our domain. Any chance that this upgrade will break these relationships for users that are using SID history for access to folders and files in their old Domains? If so what can be done to protect these trusts and SID history, prior
to moving the Domain to 2008R2

Hi,
Based on my knowledge,
the Upgrade of the function level do not affect the trust relationship.
Besides, before you upgrade the Functional Level,
verify that all DCs in the domain are, at a minimum, at the OS version to which you will raise the functional level.
Once the Functional Level has been upgraded, new DCs on running on downlevel versions of Windows Server cannot be added to the domain or forest.
For more information about function level, we can refer to following links:
Understanding Active Directory Domain Services (AD DS) Functional Levels
http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels(v=ws.10).aspx
What is the Impact of Upgrading the Domain or Forest Functional Level?
http://blogs.technet.com/b/askds/archive/2011/06/14/what-is-the-impact-of-upgrading-the-domain-or-forest-functional-level.aspx
Best Regards,
Erin

DNS EventID 4015 on PDC since Domain Migration from 2003 R2 = 2012

Hi,
following problem here:
2 Domain Controllers with AD Integrated DNS Zone, migrated from 2003 R2 to 2012. One Single Root Forest.
The Primary Domain Controller shows every 2, 3 or 4 hours the DNS EventID 4015. No further error is available: (which is may emty) "".
Only on the Details pane you can find this Information:
======================================
- System
- Provider
   [ Name] Microsoft-Windows-DNS-Server-Service
   [ Guid] {71A551F5-C893-4849-886B-B5EC8502641E}
   [ EventSourceName] DNS
- EventID 4015
   [ Qualifiers] 49152
   Version 0
   Level 2
   Task 0
   Opcode 0
   Keywords 0x80000000000000
- TimeCreated
   [ SystemTime] 2013-12-10T19:48:17.000000000Z
   EventRecordID 2456
   Correlation
- Execution
   [ ProcessID] 0
   [ ThreadID] 0
======================================
The Migration was made by the following steps:
Bring Up the first 2012 MigrationDC as 3rd DC to the Domain.
Move the FSMO Roles to the 2012 MigrationDC
DHCP Data migrated with Server Migration Tools, IAS Data with iasmigrader.exe exported
DCPromo DC1 (2003 R2) and Format C:
Install a fresh 2012 Installation on old DC1 an rename it again with the original Name DC1
DHCP Data migrated with Server Migration Tools, IAS Data with iasmigrader.exe exported
DCPromo DC2 (2003 R2) and Format C:
Install a fresh 2012 Installation on old DC2 an rename it again with the original Name DC2
Move Back the FSMO Roles to DC1
DCPromo the first 2012 MigrationDC
Metadata Cleanup for MigrationDC
DCDIAG /V /C Shows no Errors, all works good, the funny Thing is, that only DC1 Shows the DNS EventId 4015 in production evironment. The only exception is, that if you reboot DC1 (i.e. for maintenance, upates etc) than the error appears on DC2. Exactly on
that time, if DC1 is temporarily not availble and DC2 is under "load". If DC1 is back again, the Event 4015 Ends on DC2 and Comes back to DC1!!!
I backupped and restored DC1 and DC2 in an lab Environment, the funny Thing is that the EventID 4015 doesnt appear in lab Environment. The difference between prod and lab is: prod is bare metal with 2 teamed nics, lab is hyper-v vm's with 2 virtual teamed
nics. same IP's etc... DNS NIC Settings are the same.
It Looks like you can only produce the error in the production lab if you have the DC under "load".
This Event was discussed here more than one time in the Forum, but the issues doesnt match 100% to my Problem. No RODC is available in my prod Environment, the EventID 4015 has no further Errors "" in the Eventlog like in other Posts.
Ace Fekays blog :" Using ADSI Edit to resolve conflicting or duplicate AD Integrated Zones" was helpful for metadata cleanup, but it could not fix the EventId 4015 away. Because we had no Problems with disappearing zones...
Maybe Enabling NTDS Verbose Logging in the registry is helpful, but i dont know for what i have to Keep an eye out?
The thread
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c0d3adb4-67d2-470c-97fc-a0a364b1f854/dns-server-error-event-id-4015-after-replacing-domain-controller-with-another-using-same-name?forum=winserverDS seems to match to my Problem, but also no
soulution available...
Any ideas what causes this "ugly" Event without noticable consequences?

Zonenname
Typ
Speicher
Eigens
chaf
ten
Cache
AD-Domain
_msdcs.our-domain-name.com
Primary
AD-Forest
Secure
0.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.1.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
1.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
10.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
10.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
11.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
128.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
13.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
130.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
15.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
16.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
17.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
19.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
196.169.193.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
2.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
20.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
20.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
200.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
21.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
23.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
239.24.217.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
25.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
252.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.26.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
253.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
254.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
255.10.10.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
27.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
29.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
29.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.26.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
3.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
31.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
31.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
32.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
33.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
35.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
37.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
39.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
41.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
43.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
45.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
47.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
49.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.19.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
5.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
50.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
51.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
52.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
53.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
54.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
55.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
60.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
62.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
64.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
7.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
70.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
80.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
88.168.192.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.18.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.21.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.22.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.23.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.24.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.25.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.29.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
9.30.172.in-addr.arpa
Primary
AD-Domain
Secure
Rev
Aging
our-domain-name.com
Primary
AD-Domain
Secure
Agi
ng
TrustAnchors
Primary
AD-Forest

Stuck at restoring print queues while migrating from 2003 X86 to 2008 R2

i am trying to migrate from 2003 to 2008 R2 but i am stuck where it says restoring print queues and is tuckat 84% there is no error and it has not completed from pas 3 hrs now.. i have 6 print queues on it and is it normal that this willtake such long for
these 7 queues

we are getting the following error.
Log Name: Application Source: Microsoft-Windows-PrintBRM Date: 1/23/2014 5:27:15 PM Event ID: 30 Task Category: (5) Level: Error Keywords: Classic User: N/A Computer: MARPRINTPC01N1.bsci.bossci.com Description: The language monitors in the backup file
are for a different processor architecture than the destination computer. Printbrm.exe (the Printer Migration Wizard or the command-line tool) will not migrate any language monitors. Source architecture: Windows NT x86. Destination architecture: Windows x64.
Event Xml: <event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><system></system><provider EventSourceName="PrintBrm" Guid="{CF3F502E-B40D-4071-996F-00981EDF938E}" Name="Microsoft-Windows-PrintBRM"></provider><eventid Qualifiers="49154"></eventid>30</eventid><//eventid>
<version></version>0</version><//version> <level></level>2</level><//level> <task></task>5</task><//task> <opcode></opcode>0</opcode><//opcode> <keywords></keywords>0x80000000000000</keywords><//keywords> <timecreated SystemTime="2014-01-23T22:27:15.000000000Z"></timecreated><eventrecordid></eventrecordid>4174</eventrecordid><//eventrecordid>
<correlation></correlation><execution ProcessID="0" ThreadID="0"></execution><channel></channel>Application</channel><//channel> <computer></computer>MARPRINTPC01N1.bsci.bossci.com</computer><//computer> <security></security></system><//system><eventdata></eventdata><data
Name="param1"></data>Windows NT x86</data><//data> <data Name="param2"></data>Windows x64</data><//data> </eventdata><//eventdata></event>

DFS New Setup migrating from 2003 R2 file server to 2012 Server STD

We currently have a 2003 R2 flat file server with multiple layers of nested network shares with over 2.5TB of data. We want to migrate to DFS on 2012 Server standard version with deduplication enabled. We have never worked with DFS and deduplication and
any white paper on DFS and deduplication would be greatly appreciated. Not finding anything on DFS step by step for 2012 and in particular migrating from 2003 file share to 2012 server DFS.

Thank you for the URL to your DFS write up. This was very helpful in my research of DFS. I have a couple of questions. Do I have to start DFS with two servers? I completely understand why you should have more than one server in the DFS pool (high
availability) but is it necessary? Also after setting up the two 2012 Servers with DFS, namespaces, and new shares managed by DFS manager, how do we migrate (move or copy) the existing shares to new server without losing the permissions? From what I've read
in your write-up all end users with have read and write permissions and admins have full. Also is there a best practice on how nested the shares should be setup within DFS? From looking at your write up the shares are one folder deep only. At this
company I'm migrating from a file server with shares 3-8 layers deep build up over the last 20 years.

FSMO Migration from 2003 to 2008 R2

I am prepping for FSMO migration from 2003 to 2008 R2 this weekend. I was going through the steps and found a issue that is concerning me. On the 2008 server which is a DC and going to hold all FSMO roles. When I right click on Schema to change Schema
Master the "Change field" does not reflect the new 2008 R2 server? Is this by design...As in will this reflect the 2008 R2 server once I do step 1 Change Domain Controller? Single domain simple AD topology. I am an enterprise admin, domain
admin, and schema admin. The current FSMO is 2003 R2 and it follows to current 2003 R2 and 2008 R2. Will I have to seize the role?
All other FSMO moves show the new server ma-file1. Any help appreciated.
Dave Santel

All AD commands show that I have healthy replication, DNS, ect. No errors. Issue as stated above is when I goto "Change Schema Master" on ma-file1 it only gives the option to change to 2003 existing FSMO ma-file. Not sure if I should proceed with
FSMO migratio using NTDSUTIL to manually transfer? Or if anyone has any advice on how to proceed?
C:\>netdom query fsmo
Schema master               ma-file.ccc.local
Domain naming master        ma-file.ccc.local
PDC                         ma-file.ccc.local
RID pool manager            ma-file.ccc.local
Infrastructure master       ma-file.ccc.local
The command completed successfully.
C:\>netdom query dc
List of domain controllers with accounts in the domain:
MA-FILE
MA-FILE1
MA-UTILITY
The command completed successfully.
Dave Santel

Windows Migration from 2003 to 2012

Hi,
When I try to complile my vb6 code, it gives me "ActiveX component cannot create object" in half way of compiling. Advice me to get over the error.

Hi,
Did you have any migration issue during migration from 2003 to 2012?
There are several causes, for example
The class isn't registered.
A DLL required by the object can't be used, either because it can't be found, or it was found but was corrupted.
For more detail information, you could refer to this article:
http://msdn.microsoft.com/en-us/library/aa231060(v=vs.60).aspx
Meanwhile, the issue is more related to VB6 code issue, so i suggest that you may ask in vb forums for more support:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vbgeneral
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]

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Migration from 2003 - 2010, OAB errors on client, and OAB virtual directory does not contain any files.

Hi,
Please re-create the Outlook profile to have a try. If the issue persists, we can do the further checks in Exchange server.
Please make sure you have changed the OAB generation server to Exchange 2010 and enable Web distribution on the Exchange 2010 Client Access server:
Move-OfflineAddressBook "Default Offline Address List" -Server <MBX2010>
If all configurations are correct, please check whether there is any folder in the following path in Exchange sever 2010:
a. OAB generation in Mailbox:
\\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB
b. OAB distribution in Client Access:
\\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB
Thanks,
Winnie Liang
TechNet Community Support

Sharepoint migration from 2003 to office 365

Similar Messages

Maybe you are looking for