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.

Similar Messages

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

DFS-N&R Migrating from 2003R2 to 2008R2

Hello All,
I am assigned with a project of migrating existing DFS-N&R on 2003R2 to 2008R2, and decommission 2003R2 DFSservice. Is there any MS recommended howto documentation or checklist.
Apologize, if I am reposting as I checked other post, but didn't get any clear documentation.

Hi,
You can setup DFS file server on server 2008 R2, then create a replication group between the Windows 2008 R2 server and the Windows 2003 R2 server. After the DFSR replication finished, you can add the namespaces to the new serve manually and decommission the
Windows 2003 R2 DFS server.
In additional, you could use robocopy or FSMT for file copy between Windows 2008 R2 server and the Windows 2003 R2 server.
For more detailed information, please refer to the threads below:
DFS Migration from 2003 R2 to 2008 R2
http://social.technet.microsoft.com/Forums/windowsserver/en-US/697b76ca-572d-4f54-b74a-e7f3c538f524/dfs-migration-from-2003-r2-to-2008-r2?forum=winserverfiles
Best way to move DFS-shares from 2003 R2 to 2008 R2
http://social.technet.microsoft.com/Forums/windowsserver/en-US/71f72e0b-d9a7-4d06-9610-f1bf6a342aab/best-way-to-move-dfsshares-from-2003-r2-to-2008-r2?forum=winserverfiles
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

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

Can someone help me with optimal specs for a 2012 R2 server migration from 2003 R2?

My specs for the Windows Server 2003 R2 which is our file server are:
Intel Core 2 CPU 6600 @ 2.40GHz (2 CPU's), ~2.4GHz Processor types are x86 Family 6 Model 15 Stepping 6 GenuineIntel ~2399 Mhz Physical Memory is 2 GB RAM Virtual Memory is 4 GB We have 6 fixed drives in place. They all range from 300 GB to 1 TB in total space.
We have two roles on the file server in place which are File Server and WINS Server. We have QuickBooks running on it and a bunch of random smaller applications as well.
When it comes to purchasing servers, we're open to either getting all the parts and building it from the ground up or a built machine. So my question is when getting Server 2012 R2, based on what I said, what hardware should I be getting? If you need more information,
please don't hesitate to ask.
Also, if you know where I could find quality documentation on the actual migration process for a file server between 2003 R2 and 2012 R2, please let me know.
Thank you for reading. ^_^

Hi,
Since Microsoft is ending support for Windows Server 2003 R2 mid-2015, there are a bunch of resources. To partially answer your question. I came across the following blog by Jose Barreto that might be able to help.
http://blogs.technet.com/b/josebda/archive/2014/11/05/migrating-file-server-from-windows-server-2003-to-windows-server-2012-r2.aspx
Thanks,
Jeff Thai
www.AvePoint.com
Please Mark Answered if my reply solves your problem. Thanks!

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>

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

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]

Best setup for a non-Mac file server?

I have a dual xeon server, with a SATA RAID5 I want to use as a file server in a cross-platform environment.
*What I've tried and the issues...*
At first I considered using Windows 2003 (Win2k3) but Services for Macintosh (SFM) is an older version of AFP and thus only supports 31 character filenames. With all our Macs supporting SMB/Samba/CIFS and Apple touting that "Macs and PCs can co-exist harmoniously on the same network" I figured I would give that a try.
SMB doesn't work.
Sure I can create a connection, but transferring files is a completely different story. I'm trying to backup application and system data, but companies such as Adobe and Apple have named some of their files with special characters that can't be transferred over SMB. I know NTFS doesn't support these characters, but I though a Linux box using SMB would work fine. It doesn't. It's the protocol which keeps me from transferring the data. I end up with the lovely error message of "You cannot copy some of these items to the destination because their names are too long or contain invalid characters for the destination..." (what's sad is, if you google for " because their names are too long or contain invalid characters for the destination" you only get 6 results.)
So I thought I would give NFS a try. Apple says "Viewed from Mac OS X, [connecting via NFS] is just like connecting to an Apple or Windows server." No. It's not. NFS shares don't even show up in the Finder's Network listing. There are also a pile of other hurdles which are only tackled by savvy, command-line using users.
So that leaves me with AFP. Win2k3 doesn't support filenames longer than 31 characters, and Win2k8 is dropping SFM altogether. Off to choose a *nix flavor, but that requires Netatalk. It hasn't been updated in years, it has many bad performance reviews... and most distros have removed it. I can download and install it. Oh, but that requires I get the kernel source files. Then I have to create an RPM an that's not working... now I'm several levels deep in trying to figure out how to get Netatalk working and I'm not even sure it will work.
*What's the best setup for a non-Mac file server?*
FreeNAS seems promising, but it's in alpha/beta and they have all sorts of warnings regarding potential data loss. Sure there's ExtremeZ-IP, but I really don't want to spend $675 do something Apple claims OS X can already do. I can put just about any non-Mac OS on this thing... what's the best way to set it up so it works?
Thanks much.

Rick may be right because although i didnt think of it before i tend to have notoriuosly long classnames for my php classes and i have used samba on occasion (when rsync is out of the question for one reason or another) and never had a problem. I use kubuntu (feisty at the moment )with an ext3 filesystem. if i have a chance this evening ill give it a try and see what happens.
You could also possibly use FUSE to use an ssh filesystem for the shares... i don tknow how that would figure in your back up though.
Also if worse comes to worse you could tar or dmg the the necessary files... just some thoughts.
Ill be interested to know what you end up implementing....
OH one last thought... Compile Darwin from source and use that as your server

Migration from CA service desk to SCSM 2012 r2

Does any one have experience with migrating from CA Service Desk to SCSM 2012 R2?
How did you accomplish the migration

This is a common misconception about IT Service desk software, and a common reason that most helpdesk and service desk implementation fail miserably; that this something that you can just swap in and out like an email system. A service desk system isn't
just a file sharing site that you can forklift your data from and move on like before. Your service desk software is an
ERP for IT. Your Service Desk software is somewhere between a model of your IT department and a 5th column manager for your IT staff.
The typical methodology for doing this type of migration is to construct a straw model of your IT department, specifically your service book and work groups, and review your service book and incident handling procedures. once we have a solid understanding
of how your department actually runs at a conceptual and work item level, we can build a model of those work flows into service manager.
At that point, once we have a functional model of your department constructed in service manager, then we can start moving config item data. For 8 out of 10 implementations, this is better accomplished using a fresh discovery of config items from original
sources, which can then be reused to create an update methodology.
Provance's DMP (and to a lesser extent, the out of the box connectors, like the CSV connector) is a great tool for this, since it lets you build import templates that can be periodically run to update new data like purchases
for work items, a Knife edge cutover day is the simplest conversion, but certainly not the only option, that is, you decide January 15th is the day that the new system is available, and all work items go into the old system until January 14th,
and the old system will be locked for new requests on the 15th. any work in the old system is worked and closed using the usual process (even after the 15th) until the old system fades into obsolescence over the next 30 or 60 days.
You might notice that for medium enterprises (5,000 employees or so), this process typically takes several weeks of prep, and a couple of months of implementation, and it scales fairly linearly based on the size of your IT department. small departments
(somewhere below 20 analysts) can be done in a month or so, and very large IT groups, this can take a year or more.

Migrate SBS 2003 to Windows Server 2012 Standard

We currently have two servers (SBS 2003 Standard utilizing Exchange 2003; Windows Server 2003 R2 Standard with SQL 2005).
We want to retire the SBS or maybe both.
We have purchased a new server (Windows Server 2012 Standard with licenses for Exchange 2013 and SQL 2012).
Is there a whitepaper that describes how to migrate SBS 2003 to Windows Server 2012 Standard?
Is it possible to run Exchange 2013 on the Windows Server 2012 box? In Hyper-V? If Exchange can run in a virtualized instance, do we need additional licensing to run another instance of Windows Server 2012 Standard?
Can we run SQL 2012 on the same Windows Server 2012 box?
We have about 35 users.

Sal,
Migration went fine. Steps i took:
Join 2012 Standard server as member.
Migrated roles.
I ended up manually creating new shares. The old environment was a mess.
Robocopy data/verified.
Seize FSMO roles
http://support.microsoft.com/kb/255504
Metadata cleanup
http://support.microsoft.com/kb/216498
Good luck

Can I migrate from mavericks to mavericks server. Have tried using a hard drive but the but the sever does not find the migration backup when it's searches. Any help out there?

Can I migrate from mavericks to mavericks server. Have tried using a hard drive but the but the sever does not find the migration backup when it's searches. Any help out there?

Is the HDD in the 2009 15" MBP dead? (The original source of your data) If not, you might want ot take it out and put it in an enclosure.
You might try spotlight on know files to see if that gives you any clues where your data is located.
You might down load from the Internet OmniDiskSweeper (free) and open it. It should show you all of the files you have on your MBP and enable to locate them.
Ciao.

Post Migration from SP2010 -Attach File Button not working in any list new/edit forms

Hi,
We have migrated the SharePoint 2010 farm to Sharepoint 2013 on last saturday and we are noticing an interesting issue after the migration .
On any custom list on any web application ,When we create a new item,if we click on attach file button in the ribbon,nothing shows up on the screen.
In the browser Dev Tools its showing an error message as "Cannot read Property style of null".
This is happening on a javascript (form.debug.js) on line No : 5276
(document.getElementById("partAttachment")).style.display = "block";
There is no element rendered in html with id "partAttachment",which is causing this error to happen.
Solutions tried are
1) Modified the List Advanced Settings to disable and enable the attachments ,which did not work
2) Ran the Sharepoint Configuration wizard which did not fix
3)Tried reset the site definition for all pages in the site from site settings
4) Deactivated and activated all the activated features in the site collection
Its an OOB List New Form,no customizations has been done.
Similar error occurring with List Edit form as well
when you click on the List Item in the List default view when you navigate to the list and when you click on attach file,a popup dialog to upload attachments appearing,However its not working when you
navigate into the list item and tried to upload attachment.
Please help if any Solutions / thoughts

Hi Christopher,
Thanks for your reply,
Farm Information
OS: Windows Server 2008 R2 SP1 Enterprise
SQL: SQL 2008 R2 SP2
SP -SharePoint 2013 with no CU applied
Method,we used is restored the content DB from SP2010 and attaching to SP2013 SQL Server
Site Collection is in 15 mode
It happens on new site collection even though its not migrated site.
Server is 16GB RAM 8Core Processor
If we create a new form from designer,attach file link is working
OOB New form.aspx is having List Form webpart
Custom New Form.aspx creaed with designer has data form webpart
if we create a new sharpoint site collection in 2010 mode,its working fine without any issues
Interestingly,all the javascript files loading were debug.js,Not sure how its loading all debug.js files

New iMac, migrated from macbook and now mail won't work. Tried re-installing operating system, still doesn't work. Can anyone help me to get mail working? thanks

I just bought a new iMac and I thought that it would be simple to migrate from my MacBook.
I have a time machine back-up so I decided to migrate using that. Everything seemed to instal pretty well with the exception of mail. To begin with I had 2 mail icons, then I started to read some forums and checked that i had the one I wanted in the applications folder, deleted the other and then downloaded the new operating system. Mail had to be force quit first and even when the download was complete Mail still wouldn't open or run. The only thing I can do is compose a new message, but I can't see my inbox at all.
It's really frustrating and I would love to know in a simple step by step guide how to get mail up and running with my existing migrated emails in it.
If anyone can give me some advice that would be great.
thanks in advance.
H

Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash.
Triple-click the line below to select it, then copy the selected text to the Clipboard (command-C):
find ~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 -o -acl $ 2> /dev/null | wc -l
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
The output of this command, on a line directly below what you entered, will be a number such as "41." Please post it in a reply.

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

Similar Messages

Maybe you are looking for