Domain Migration :from single domain to multiple domain.

Hi ,
We have an urgent requirement for the domain migration
The scenario is currently we are using MS AD as LDAP server to store portal users and thier credentials.
Lets say we have current domain name as : ad.abc.com
we are planning to migrate from this domain to number of domains.our requirement is to move the portal users into thier specific domain in batches.eg out of 5 users 2 has been moved to new domain and other 3 are still in ad.abc.com.
But after domain migration ,all the 5 users should be able to access all the applications and functionality of portals.
What should we do to achieve the same?
How portal applications will be affected by this?Can all the users access all applications without fail?
What exactly the LDAP does in portals?
Any help will be greatly appreciated
Thanks in Advance
Amit

Hi,
Yes, you need to prepare Active Directory and domains.
What's more, you need to upgrade existing Exchange 2007 servers to Exchange 2007 Service Pack 2 at least.
Here is an article for your reference.
Exchange 2007 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/dd638158(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

Domain migration: From single domain to Multiple

Hi ,
We have an urgent requirement for the domain migration
The scenario is currently we are using MS AD as LDAP server to store portal users and thier credentials.
Lets say we have current domain name as : ad.abc.com
we are planning to migrate from this domain to number of domains.our requirement is to move the portal users into thier specific domain in batches.eg out of 5 users 2 has been moved to new domain and other 3 are still in ad.abc.com.
But after domain migration ,all the 5 users should be able to access all the applications and functionality of portals.
What should we do to achieve the same?
How portal applications will be affected by this?Can all the users access all applications without fail?
What exactly the LDAP does in portals?
Any help will be greatly appreciated
Thanks in Advance
Amit

Hi,
Yes, you need to prepare Active Directory and domains.
What's more, you need to upgrade existing Exchange 2007 servers to Exchange 2007 Service Pack 2 at least.
Here is an article for your reference.
Exchange 2007 - Planning Roadmap for Upgrade and Coexistence
http://technet.microsoft.com/en-us/library/dd638158(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Single login for multiple domains

Can anyone point out a blog or post of a single login for
multiple domains? For example, let's say I own asite.com and
bsite.com.
I want a user who logins to asite.com to also be logged into
bsite.com if they visit that site. BSite.com is clearly a microsite
of asite.com but we'd like to continue to use that domain if the
visitor is on that site instead of redirecting them to keep login
credentials
Thanks

If you're using cookie based login system, I'd imagine you
could set a cookie to be valid for both of your sites.
<cfcookie name="myAuthcookie" value="myAuthValue"
domain=".asite.com;.bsite.com">
That way both asite.com and bsite.com can read your cookie.
Note the notation; always include the preceeding dot in the domain
values. (two dots for top level domains, etc.)
Strangely CFCOOKIE documentation doesn't mention anything
about using semicolon separating multiple domains. It did in CF5
documentation, but not since.

How does a RAC DB 'spread' from single instance to multiple instances ?

GI/RDBMS Version: 11.2.0.3
OS: Oracle Linux 6.3
Filesystem : ASM
When a RAC database is created using dbca , Manually , or RMAN restore, the DB is created in the Node1 first with cluster_Database=FALSE .
Then you run the following commands (for 3-node RAC) from Node1
srvctl add database -d lmnprod -o $ORACLE_HOME -p +LMNPROD_DATA01/lmnprod/spfilelmnprod.ora
srvctl add instance -d lmnprod -i lmnprod1 -n hwcarser290
srvctl add instance -d lmnprod -i lmnprod2 -n hwcarser291
srvctl add instance -d lmnprod -i lmnprod3 -n hwcarser292
Once the DB is created,mounted and opened in Node1 and the above commands are executed , you set cluster_Database=TRUE and startup the Instance2 and Instance 3 in Node2 and Node3.
I just want to know how does Node2 and Node3 becomes aware of the DB and joins the DB cluster ? What happens internally ?

Generally speaking, registering in OCR is not required for database to be a cluster database.
Migration from single-instance database to cluster consists of creating redo logs and undo tablespace for new instance and enabling this instance (thread). If database is policy-managed, this is done automatically for new node.

Migrate from single instance to RAC manually

Hi,
I have a 10g database running in single instance.I have installed grid 11.2.0.2 in two nodes including the node where current instance is running,I have installed 10g again in a seperate mount point in both the nodes .It has the same patches as single instance 10g home.Now how to migrate from single instance to RAC manually.
Thanks,
Sekar

-restore this database into 11g ASM if its not already on ASM.
-upgrade this database to 11g from 10g on single instance.
-Now Converting Single Instance on a Cluster to Oracle RAC ,here you have different option to perform this once its 11g database after upgrade.
using rconfig
using dbca or manually.
see detail here
http://docs.oracle.com/cd/E11882_01/install.112/e24660/cvrt2rac.htm#autoId9

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

MDT from Single Site for Multi Domain OS Deployment

Hi all,
We are looking for a solution which will make it possible to use MDT from a single site to deploy Windows 7 or Windows 8 and join different domains of different customers without trust relationships between domains.
We are a service provider which supports different customers with separate domains. At this moment those different customers have their own WDS server on site and administration is time consuming because a lot of hardware changes occur.
We are now searching for a solution which is easier to manage and one of the solutions we are thinking about is to install a WDS server in our office and use MDT for some custom task sequences but just build one image with all the different driver packs we
have.
Does anyone know how to deal with this from our point of view. All tooling I can find is based on Enterprise clients with one Domain Forest and maybe some different sites but all in one domain, which makes deployment a bit easier then in our situation I guess
as we are looking for a solution that supports Multi-domain deployment.
Hope someone might experienced this before and can help us in the right direction. If someone has experience with additional tooling which might help us I am more then interested to know how the tooling helped in solving this.
Preferrably we had a tool which was Multi-tenant and multiple domains could be managed from a single console, but I think that tool just doesn't exist.
Hope someone is able to help us in the right direction. Please let me know if you have any tips or did experience the same while making a Deployment plan for the service provider you are working for.
Many thanks in advance!

Hi all,
We are looking for a solution which will make it possible to use MDT from a single site to deploy Windows 7 or Windows 8 and join different domains of different customers without trust relationships between domains.
We are a service provider which supports different customers with separate domains. At this moment those different customers have their own WDS server on site and administration is time consuming because a lot of hardware changes occur.
We are now searching for a solution which is easier to manage and one of the solutions we are thinking about is to install a WDS server in our office and use MDT for some custom task sequences but just build one image with all the different driver packs we
have.
Does anyone know how to deal with this from our point of view. All tooling I can find is based on Enterprise clients with one Domain Forest and maybe some different sites but all in one domain, which makes deployment a bit easier then in our situation I guess
as we are looking for a solution that supports Multi-domain deployment.
Hope someone might experienced this before and can help us in the right direction. If someone has experience with additional tooling which might help us I am more then interested to know how the tooling helped in solving this.
Preferrably we had a tool which was Multi-tenant and multiple domains could be managed from a single console, but I think that tool just doesn't exist.
Hope someone is able to help us in the right direction. Please let me know if you have any tips or did experience the same while making a Deployment plan for the service provider you are working for.
Many thanks in advance!
So is the goal is not only to get multiple domains to select from, if so you could use a DomainOUList.xml file .
Also would the clients be imaged at your site or your clients site?
If this post is helpful please click "Mark for answer", thanks! Kind regards

Migrated domain replication from FRS to DFSR. Domain query

Hello,
I run 3 domain controllers, all on the same LAN; the PDC is on 2008R2 and the others on 2012
I have today migrated from FRS to DFSR.
Without going through all the errors that dcdiag is now showing, I have a simple query. When our domain was setup, it was named COMPANY ie. not COMPANY.LOCAL. It has all seemed to work OK for ages but in DNS Forward Lookup Zones I see
the following folders:
_msdcs.company
company
company.company
In company.company are just the 3 domain controllers. Can I delete this folder?
Other question at this stage is about DNS forwarders. All LAN PCs point to the 3 x DCs for their DNS servers, and DNS Server is running on all 3 DCs. Should I put my ISPs DNS servers in the forwarders or not, and do I use root hints? (I have 2 ISPs so don't
know which ISP will be used by any PC as the router load balances)
many thanks in advance

Hi,
Yes, i think you could delete the folder, if the replication is ok.
You could use your ISPs DNS server as a forwarders.
http://blogs.technet.com/b/tugait/archive/2014/02/11/dns-forwarders-vs-root-hints.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]

Migrate from single server to multiserver path?

I'm looking to move from a single Exchange 2013server to multi server for HA, i.e. multiple database servers and client access servers. What the best way to migrate? I would like to keep the existing single server as a client access server. I'll
be using a hardware load balancer for the client access servers. Existing 2013 Exchange server has Windows 2012 Datacenter installed.
Can just make a new database sever and create a DAG then create a new client access server then configure the load balancer?
Thanks for any input on how to migrate from a single server to multiple server for additional HA.

Is there any benefit to using Server 2012 R2 vs Server 2012 R1? The single server is currently Server 2012 R1. Can I do an in place upgrade from 2012 R1 to R2 without messing up Exchange?
Here's my thoughts so far:
1. Make 3 additional 2012 R1 servers
2. On 2 of the servers install additional Exchange servers with mailbox database roles (it appears each new mailbox server comes with a database which I'll delete).
3. On the last new server, install CAS role
4. Create DAG with all 3 servers with database role
5. Add production database copies to DAG
6. Configure load balancer for CAS load balancing
Thoughts? Is the production database on the single server available while a copy is being made to the new mailbox database servers? Also, I thought I read some where to move mailboxes to DAG, but I don't see why if I can just add copies of the existing
database to the DAG group.

Migration from Single Node to RAC Node

Hi,
We are planning to migrate the Database from Single-Node to RAC Node. Are there any checklist list to be considered regarding Performance, System and Database ( or any other topic), before migrating to RAC.
Thanks

If it is already the same version, you will need to focus any "single-threadedness" of the application like sequences that are mandatory sequential, "semaphore-style" locking etc...
My experience is that going RAC and in particular to ASM can give a performance boost. If it is the same version (11gR2 for example) then any statistics-related performance issues will still be there.

Migrating from single-node to multi-node (2 Node)

Hi,
We have decided to migrate our existing 11.5.9 application from single-node to 2 Node(multi-node). Please let me know what services should reside on each node (Recommended by Oracle).
Forms, Reports, Apache on one node and CM, Admin, DB on another ?
(or)
DB on one node and all other on another node ?
And please let me know the steps I should follow to achieve the task as well.
Thank & Regards,
Abdullah

Hi;
I suggest please review our previous posts and check notes:
shared appltop/distributed appltop
Re: two nodes
In R12 shared appltop/distributed appltop
shared appltop -Which node
Re: shared appltop
Shared appltop in R12
Shared appltop in R12
shared APPL TOP or shared application
shared APPL TOP or shared application
Regard
Helios

Migrating from single processor to dual processor Callmanager

Hi Networkers,
had anyone install a Callmanager 4.1 dual processor version of CM4.1-K9-X345D= before in a single CPU in a dual processor capable server before.
Can it work in the first place?
Had anyone successfully migrate it to a dual-processor later on?

I dont think there is any difference in Callmanager software for a dual processor versus single processor server. For 7845 (dual processor) the hardware detection disks may be different from the one for single processor (7825, 7835)
Migrating from one to another is as easy as taking a BARS backup from one server, build the other server to the same version and restore it. (Make sure server name and ip are the same for both servers)
Please remember to rate posts!

Faster way to migrate from Single byte to Multi byte

Hello,
We are in the process of migrating from a 9i Single byte db to a 10g Multi byte db. The size of our DB is roughly 125 GB. We have fixed everything in the source database (9i) in terms of seamlessly migrating from a single byte to a multi byte db. The only issue is the migration window - curently we are doing an export/import since there is a character set migration involved and it's taking about 20+ hrs to do the import in 10g. The management wants to cut this down to less than 10 hours, if that's possible. I know the duration it takes to import depends on many factors like the system/OS configuration, SAN, etc but I wanted to know what , in theory, is considered the fastest method of migrating a database from single byte to multi byte.
Have anybody here gone through this before?
Thanks,
Shaji

If the percentage of user tables containing some convertible data (I am assuming you will not have any truncation or lossy data) is low, you can export only those tables, truncate them, and rescan the database. This should report no convertible data, except some CLOBs in Data Dictionary. Such database can be migrated to AL32UTF8 using csalter.plb. After the migration, you import only the previously exported subset of tables.
Note, for this process to work, no convertible VARCHAR2, nor CHAR, nor LONG data can be present in the Data Dictionary.
The process should be refined by dropping and recreating indexes on the exported tables as recreating an index is faster then updating it during import. You should also disable triggers so that they do not interfere with the migration (for example, they should not update any "last_updated" timestamp columns).
If the number and size of affected tables is low compared to the overall size of the database, the time saved may be significant.
There may also be tables that require even more sophisticated approach. Let's say you have a multi-gigabyte table that stores pictures or documents in a BLOB column. The table also has a single text column that keeps some non-ASCII descriptions of the stored entities. Exporting/truncating/importing such table may be still very expensive. A possible optimization is to offload the description column to an auxiliary table (together with ROWIDs), update the original column to NULL, export the auxiliary table, drop it, rescan the database, migrate with csalter.plb, re-import the auxiliary table, and restore the original column. If pictures alone occupy, for example, 30% of the whole database, such approach should yield significant time saving.
-- Sergiusz

"Can Portal Authenticate a single user into multiple Domains"

Hi All,
I have a requirement in the following way.is it Possible to achieve?
lets take user with user-id(SSO environment) ABC ,maintained in MS AD under domain name say "SAP.com"
We are going to migrate this domain into another domain say "SAP123.com" and so others,and we want to maintain the same user with same userID in new domain(SAP123.com) also.
In simple words user must be able to authenticate on both domains and he should be able to access all the applications in new domain also via role mechanism
This we are going to do only for test purpose,later we will be maintaining only 1 domain for 1 user.
My only question : is it possible to accomplish the above requirement by any means?and How?Does it make sense?
waiting for your valuable inputs.
Thanks in Advance
Amit Koyal

Hi Amit,
yes, I'm around, but unfortunately pretty busy at the moment (preparing the TechEd session for Amsterdam next week).
Here my answers:
1. As you can read from SAP Note 762419, "it is possible to use integrated Windows authentication in a multi-domain environment even if users' logon IDs (represented by the attribute "samaccountname") are not unique across all domains". Please make sure that you go through the limitations of the two options.
2. If you change the portal domain, SSO will work only with servers located in the same (new) domain as the portal. You don't need to make here any change if your (SAP) applications are also in the new domain. If not, please consult the documentation I gave you in my previous post.
Hope this helps,
Robert

Migrate from whs11: how do non-domain backups work?

Hello, I'm looking at moving from whs11 to wse12r2. The main question I have is how do I handle backups for non-domain joined machines. Is this supported/seamless?
Thanks.

Hi,
Do you mean that you want to migrate the backup saved on whs11 to wse12r2 and the backup can still be restored by the wse12r2? If so, you cannot use the backup because System State Recovery is only supported on the same operating system instance. It is not
supported on a reinstalled operating system on the same or different hardware.
For more detailed information, please refer to the article below:
How to restore a Windows installation or move it to different hardware
http://support.microsoft.com/kb/249694
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.

Domain Migration :from single domain to multiple domain.

Similar Messages

Maybe you are looking for