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]

Similar Messages

General SYSVOL migration from FRS to DFSR

Hi all.
I have a question regarding Sysvol Migration from FRS to DFSR.
We have migrated all of our Domain Controllers from Server 2003 to Server 2008 R2 about 2 years ago.
I know that if Server 2003 was in use initially and you upgrade to Server 2008 R2, you need to do a FRS to DFSR migration in order for you Sysvol to make use of DFSR.
My question is if we are upgrading now to server 2012 R2 would there be a time that this would happen automatically or do we still need to do the sysvol migration before upgrading to server 2012 R2.
Another question I have is do we need to do the FRS to DFSR migation on all our child domains as well ?
Many thanks for your time.
Your answers would be appreciated.
Kind Regards,
Shaun

Hi There.
Yes that would be great. I would probably use the active directory removal method but I dont know if this would work as its the last domain contoller and it is not replicating with the top level domain at the moment.
NTDSUTIL would probably need to be used ro list the servers in that domain and remove them and then if I'm correct I would need to remove the domain namig contect with the instructions below.
Removing Orphaned Domains from Active Directory
Determine the domain controller that holds the Domain Naming Master Flexible Single Master Operations (FSMO) role. To identify the server holding this role:
Start the Active Directory Domains and Trusts Microsoft Management Console (MMC) snap-in from the
Administrative Tools menu.
Right-click the root node in the left pane titled
Active Directory Domains and Trusts, and then click Operations Master.
The domain controller that currently holds this role is identified in the Current Operations Master frame.NOTE: If this changed recently, not all computer may have received this change yet due to replication.
For more information about FSMO roles, click the following article number to view the article in the Microsoft Knowledge Base:
197132 Windows 2000 Active Directory FSMO Roles
Verify that all servers for the domain have been demoted.
Click Start, point to Programs, point to
Accessories, and then click Command Prompt.
At the command prompt, type: ntdsutil.
Type: metadata cleanup, and then press ENTER.
Type: connections, and then press ENTER. This menu is used to connect to the specific server on which the changes will occur. If the currently logged-on user is not a member of the Enterprise Admins group, alternate credentials can be supplied
by specifying the credentials to use before making the connection. To do so, type:
set creds domainname username password , and then press ENTER. For a null password, type:
null for the password parameter.
Type: connect to server <var>servername</var> (where <var>servername</var> is the name of the domain controller holding the Domain Naming Master FSMO Role), and then press ENTER. You should receive confirmation that the connection is successfully
established. If an error occurs, verify that the domain controller being used in the connection is available and that the credentials you supplied have administrative permissions on the server.
Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
Type: select operation target, and then press ENTER.
Type: list domains, and then press ENTER. A list of domains in the forest is displayed, each with an associated number.
Type: select domain <var>number</var>, and then press ENTER, where <var>number</var> is the number associated with the domain to be removed.
Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
Type: remove selected domain, and then press ENTER. You should receive confirmation that the removal was successful. If an error occurs, please refer to the Microsoft Knowledge Base for articles on specific error messages.
Type: quit at each menu to quit the NTDSUTIL tool. You should receive confirmation that the connection disconnected successfully.
Thanks again for all your help.
Regards.
Shaun

FRS and DFSR replication

Hi all,
fase 1
My domain controllers are both Windows 2003 R2 and Windows 2008 and Windows 2008R2. Domain functional level is Windows 2003
fase 2
I upgrade all my domain controllers to Windows 2008R2 and raised the domain functional level to Windows 2008R2.
Now do domain controllers replicate via DFS-R? Have I to make some operation to get all replication works via DFS-R?

Hi,
Domain controllers use a special shared folder named SYSVOL to replicate logon scripts and Group Policy object files to other domain controllers. Windows 2000 Server and Windows Server 2003 use File Replication Service (FRS) to replicate SYSVOL, whereas
Windows Server 2008 uses the newer DFS Replication service when in domains that use the Windows Server 2008 domain functional level, and FRS for domains that run older domain functional levels.
To use DFS Replication to replicate the SYSVOL folder, you can either create a new domain that uses the Windows Server 2008 domain functional level, or you can use the procedure that is discussed in this document to upgrade an existing domain and migrate
replication to DFS Replication.
There are many helpful articles for you to refer to to migrate sysvol replication form FSR to DFSR. Please refer to the below link to find a article you want to follow:
http://blogs.technet.com/b/askds/archive/2009/05/01/sysvol-migration-from-frs-to-dfsr-whitepaper-released.aspx
Regards,
Yan Li
Yan Li
TechNet Community Support

FRS to DFSR Migration and Riverbed RODCs

As I understand it, Riverbed RoDCs are only there to grab session keys from AD in order to optimize SMB traffic. Please correct me if I'm wrong.
I'm in the middle of trying to migrate from FRS to DFSR for SYSVOL, but when moving from the Start to Prepared state, DFSRMig complains that the Riverbed RoDCs aren't following.
C:\Users\adminaccountname>dfsrmig /getmigrationstate
The following Domain Controllers are not in sync with Global state ('Prepared'):
Domain Controller (Local Migration State) - DC Type
===================================================
xxx1a-xxx-xx05 ('Start') - Read-Only DC
xxx1a-xxx-xx03 ('Start') - Read-Only DC
xxx1a-xxx-xx04 ('Start') - Read-Only DC
Pretty sure this is entirely out of my control and there might be a mode of operations on the Riverbed side that needs to be raised along with the functional level of the forest and domain, but I'm getting nothing from the Riverbed documentation that I can
get my hands on. I'm waiting to hear from our networking team.
In the meantime, has anyone had any experience with this?

Hi,
Migration from one stable state to another can take an extended period, especially if some of the domain controllers are read-only. In these cases, migration may not reach a consistent state on all domain controllers for a long time after you change the
global migration state.
For more and detail information, please refer to:
Troubleshooting SYSVOL Migration Issues
http://technet.microsoft.com/en-us/library/dd639976(v=ws.10).aspx
Hope this helps.
Regards.
If you have any feedback on our support, please click
here
Vivian Wang

FRS to DFSR migration (Child domain)

Planning on migrating FRS to DFSR for a child domain, I know this is a per domain process.
It shouldn't matter which domain is migrated first, the child or root. But to doublecheck : The plan is to migrate they child domain and the root domain will take a couple of months before it's prepared. Does it matter? Even though i'm pretty certain it
doesn't matter because it's a per domain process, but wanted to verify.

> It shouldn't matter which domain is migrated first, the child or root.
No, it doesn't.
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

SCCM 2012 R2 User State Migration Win XP to Win 8.1 does not migrate Domain User Files

Hi @ all
i'm trying migrate Win XP Sp3 to Win 8.1 using SCCM 2012 R2. So i followed the how to from the SCCM Team.
https://blogs.technet.com/b/configmgrteam/archive/2013/09/12/how-to-migrate-user-data-from-win-xp-to-win-8-1-with-system-center-2012-r2-configmgr.aspx
All things worked fine, but the user files from my test Domain user are not restored.
Here some extracts of the loadstate log.
2014-01-07 15:49:16, Info                  [0x000000] User SCCM\test.user maps to S-1-5-21-2486663232-1734351201-1738771205-1113
2014-01-07 15:49:16, Info                  [0x000000] User TEST-COMPUTER\Administrator maps to TEST-COMPUTER\Administrator
2014-01-07 15:49:16, Error                 [0x000000] The account TEST-COMPUTER\User is chosen for migration, but the target does not have account TEST-COMPUTER\User. See documentation
on /lac, /lae, /ui, /ue and /uel options.
2014-01-07 15:49:16, Info                  [0x000000] Failed.[gle=0x00000006]
2014-01-07 15:49:16, Info                  [0x000000]   Unable to create a local account because /lac was not specified[gle=0x00000006]
2014-01-07 15:49:16, Info                  [0x000000] Entering MigCloseCurrentStore method
2014-01-07 15:49:16, Info                  [0x0801dc] Closing catalog file
2014-01-07 15:49:16, Info                  [0x0801dd] Deleting catalog file at C:\Windows\Temp\tmpF6E7.tmp\Temp\tmp9F3.tmp
2014-01-07 15:49:16, Info                  [0x000000] Leaving MigCloseCurrentStore method
2014-01-07 15:49:16, Info                  [0x000000] USMT Completed at 2014/01/07:15:49:16.078[gle=0x00000057]
The user sccm\test.user is my test user but, i cannot see any error in relation to that user.
Has some some an idea?
Thank you
Adrian

Hi,
I found a similar article for your reference.
http://blogs.technet.com/b/sudheesn/archive/2009/12/28/in-place-upgrade-from-windows-xp-to-windows-7.aspx
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.

JSP not working on migrated domain

          I migrated my Weblogic 5.1 properties file to Weblogic 6.0
          using the console.
          I am unable to invoke the HelloWorld.jsp from a browser when I
          place it in my \applications\DefaultWebApp-myServer directory.
          My migrated server listens on port 7001 and I used the URL to invoke
          HelloWorld:
          http://208.139.197.151:7001/HelloWorld.jsp
          When I placed it in the examples'
          applications\DefaultWebApp-examplesServer it worked.
          My examples server listens on port 7003 and I used the following
          URL to invoke HelloWorld:
          http://208.139.197.151:7003/HelloWorld.jsp
          I'm attaching my config.xml for the migrated domain.
          Thanks,
          Shelly
          [config.xml]


          Kumar,
          This solved the problem!
          Thanks,
          Shelly
          Mettu Kumar <[email protected]> wrote:
          >Shelly,
          >
          > I guess I got what the problem is.
          > Check your web.xml of default app. During migration
          >from 5.1 to 6.0 JSPServlet
          >might be registed as servlet without init parameters.
          >Remove those lines related to
          >JSPServlet.
          >
          >Hope this solves your Problem.
          >
          >
          >Thanks,
          >Kumar.
          >
          >Shelly wrote:
          >
          >> Attached is the log.
          >> Thanks
          >> Mettu Kumar <[email protected]> wrote:
          >> >If you can post the server out setting you debug output
          >> >level to info it will be
          >> >easy to trace the problem.
          >> >
          >> >Shelly Foland wrote:
          >> >
          >> >> Kumar,
          >> >>
          >> >> Thanks for looking at my config.xml.
          >> >>
          >> >> I did try changing the path as you specified below
          >> >> and I still have a problem.
          >> >>
          >> >> I wonder if this is related to the fact that I migrated
          >> >> this domain from 5.1?
          >> >>
          >> >> Shelly
          >> >>
          >> >> Mettu Kumar <[email protected]> wrote:
          >> >> >The reason is straight forward.
          >> >> >
          >> >> >The following lines in your config.xml:
          >> >> > <Application
          >> >> > Name="DefaultWebApp_myserver"
          >> >> > Path="config\Weblogic5.1\applications"
          >> >> > >
          >> >> >
          >> >> >Change the path to ".\config\mydomain\applications"
          >> >> >
          >> >> >Hope this helps you.
          >> >> >
          >> >> >Kumar.
          >> >> >Shelly Foland wrote:
          >> >> >
          >> >> >> I migrated my Weblogic 5.1 properties file
          >> >> >to Weblogic 6.0
          >> >> >> using the console.
          >> >> >>
          >> >> >> I am unable to invoke the HelloWorld.jsp from
          >> >> >a browser when I
          >> >> >> place it in my \applications\DefaultWebApp-myServer
          >> >> >directory.
          >> >> >>
          >> >> >> My migrated server listens on port 7001 and
          >> >> >I used the URL to invoke
          >> >> >> HelloWorld:
          >> >> >>
          >> >> >> http://208.139.197.151:7001/HelloWorld.jsp
          >> >> >>
          >> >> >> When I placed it in the examples'
          >> >> >> applications\DefaultWebApp-examplesServer
          >> >> >it worked.
          >> >> >>
          >> >> >> My examples server listens on port 7003 and
          >> >> >I used the following
          >> >> >> URL to invoke HelloWorld:
          >> >> >> http://208.139.197.151:7003/HelloWorld.jsp
          >> >> >>
          >> >> >> I'm attaching my config.xml for the migrated
          >> >> >domain.
          >> >> >>
          >> >> >> Thanks,
          >> >> >> Shelly
          >> >> >>
          >> >> >> ------------------------------------------------------------------------
          >> >> >> Name: config.xml
          >> >> >> config.xml Type: BizTalk Schema (text/xml)
          >> >> >> Encoding: base64
          >> >> >
          >> >
          >>
          >> ------------------------------------------------------------------------
          >> Name: startWL.log
          >> startWL.log Type: Text Document (application/x-unknown-content-type-txtfile)
          >> Encoding: base64
          >

Ldm migrate-domain failure

Hi!,
Any time i'm trying to use ldm migrate-domain on my system, i'm getting following error:
Failed to connect to logical domain manager: Connection refused
XMPP connection failed
# svcprop svc:/ldoms/ldmd:default
general/enabled boolean true
general/action_authorization astring solaris.smf.manage.ldoms
general/entity_stability astring Unstable
general/single_instance boolean true
ldmd/debug integer 0
ldmd/hops integer 0
ldmd/incoming_migration_enabled boolean true
ldmd/nocfg boolean false
ldmd/outgoing_migration_enabled boolean true
ldmd/xmpp_enabled boolean true
fmd_config/fmd_to_ldmd_init_timeout integer 20
fmd_config/fmd_to_ldmd_running_timeout integer 10
filesystem/entities fmri svc:/system/filesystem/local
filesystem/grouping astring require_all
filesystem/restart_on astring none
filesystem/type astring service
start/exec astring /opt/SUNWldm/bin/ldmd_start
start/timeout_seconds count 180
start/type astring method
stop/exec astring :kill
stop/timeout_seconds count 180
stop/type astring method
tm_common_name/C ustring Logical\ Domains\ Manager
restarter/logfile astring /var/svc/log/ldoms-ldmd:default.log
restarter/contract count 246
restarter/start_pid count 2564
restarter/start_method_timestamp time 1235404992.535367000
restarter/start_method_waitstatus integer 0
restarter/auxiliary_state astring none
restarter/next_state astring none
restarter/state astring online
restarter/state_timestamp time 1235404992.548580000
restarter_actions/restart integer
I checked /var/svc/log/ldoms-ldmd:default.log, and noticed, that every boot my ldm returns:
[ Feb 23 18:03:10 Executing start method ("/opt/SUNWldm/bin/ldmd_start") ]
Added to channel ds, service md-update, versions 1.0
Added to channel ds, service domain-shutdown, versions 1.0
Added to channel ds, service domain-panic, versions 1.0
Added to channel ds, service dr-cpu, versions 1.1 1.0
Added to channel ds, service keystore, versions 1.0
Added to channel ds, service fma-cpu-service, versions 1.0
Added to channel ds, service dr-crypto-mau, versions 1.0
Added to channel ds, service dr-crypto-cwq, versions 1.0
Added to channel fmactl, service fma-phys-mem-service, versions 1.0
Added to channel ds, service var-config, versions 1.0
Added to channel ds, service fma-mem-service, versions 1.0
Added to channel fmactl, service fma-pri-service, versions 1.0
Added to channel ds, service dr-vio, versions 1.0
Added to channel fmactl, service fma-phys-cpu-service, versions 1.0
Added to channel spds, service pri, versions 1.0
Added to channel spds, service mdstore, versions 1.0
warning: rng-#units propval (1) doesn't match number of RNG exec-units nodes in PRI (0)
warning: vswitch node missing vlan-id property
warning: vswitch node missing vlan-id property
warning: vswitch node missing vlan-id property
warning: vswitch node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: vnet node missing vlan-id property
warning: Failed to load certificate chain from file
warning: server CTX setup failed
warning: SSL setup failed. Migration and XMPP server will not be usable.
Power Management starting.
[ Feb 23 18:03:12 Method "start" exited with status 0 ]
# pkginfo | grep openssl
system SUNWopenssl-commands OpenSSL Commands (Usr)
system SUNWopenssl-include OpenSSL Header Files
system SUNWopenssl-libraries OpenSSL Libraries (Usr)
system SUNWopenssl-man OpenSSL Manual Pages
system SUNWopensslr OpenSSL (Root)
# ldm -V
Logical Domain Manager (v 1.1)
Hypervisor control protocol v 1.3
Using Hypervisor MD v 0.1
System PROM:
Hypervisor v. 1.7.0 @(#)Hypervisor 1.7.0 2008/12/11 13:38\015
OpenBoot v. 4.30.0 @(#)OBP 4.30.0 2008/12/11 12:15
What is wrong ?
Thanks for help

Only now i noticed, that i created this topic in wrong category. Sorry about that. :/

Migrate Domain Controller include Exchange Server

Beside the above suggestions, you may also walk through this informative technet article that covers almost all the required steps and provides step-wise instructions to accomplish this task in simple way : http://blogs.technet.com/b/chrisavis/archive/2013/10/01/performing-an-in-place-upgrade-of-server-200... When you will be migrating users mailboxes from old server to upgraded server, you can have a look on Lepide exchange manager that would be a suitable approach to get this job done in flawless manner without having downtime.

Hi everybody !
My company bought a new server and I have schedule to migrate current domain controller ( 2008 R2 ) to new server ( 2012 R2 )
My system has 1 Exchange server which I'm not familiar with. I have experience with migrating DC ( transfer roles / DNS ) but I'm worry about Exchange server. What should I prepare for this case ?
This topic first appeared in the Spiceworks Community

Migrating DC's from Server 2003 to Server 2008 Enterprise R2

I am in the process of testing a migration of our DC's to 2008 R2.
I've read countless articles, step by steps, etc, but am still having trouble deciding the best way to figure this thing out. Hoping that someone can give me some pointers on what might be the best way to do this. It should be fairly straightforward but
I am just unsure of how the fact that the two DC's being on different networks & the DFS will play in to things.
I currently have
(1) PDC residing in a colo (172.16.36.x) Server 2003
(1) Mail server residing in a colo (172.16.36.x) Server 2008
(1) DC residing in our office (172.16.35.x) Server 2003
These 2 different networks are connected by VPN from our office to the colo.
The DC in the office is running DHCP and DNS. It also acts as the File Server. The data is then being replicated using DFS from the office DC to the colo PDC.
We have purchased 2 new servers (physical) to replace the DC and PDC and also am installing Server 2008 R2.
From what I've gathered, I should join these new machines to the domain and begin migrating.
Step 1: Install Active Directory on new Servers, Install/Migrate DNS?
Step 2: Transfer Roles (Looking for recommendation as to which DC acts for which Role also, or should the PDC hold all roles?)
Step 3: Migrate files/shares and set up DFSR?
If anyone can offer some advice on how to make this as simple as possible I would greatly appreciate it!

Thanks for the link. I've been able to successfully migrate almost everything over, just had a few questions about DFSR.
This is the scenario:
Server A (old file server, located in office)
Server B (old file server, located in colo)
Server C (new file server, located in office)
Sever D (new file server, located in office)
I have 2 servers currently. Both running Server 2003 (DFS) acting as file servers. Server A is the preferred connection when using DFS, so typically any changes from users will be made on Server A and then replicated to Server B. I've tested the File
Server Migration Toolkit to migrate files/shares over from server B to Server D, it seems to work fine. Now, I am not sure what the best way to migrate everything would be.
This was my thought process but I am not certain this is the best way/or will work as intended.
Use FSMT to copy all shares from Server A to Server C.
Plan for short downtime to copy all open files from Server A to Server C.
Map users to shares on Server C.
Begin replication from Server C to Server D. When complete map users to DFSR link.
Then take Server A and B offline.
Something I wasn't sure about is maybe using FMST to migrate things from Server B to Server D. Would it then compare to Server C through DFSR or does this replication have to occur "naturally"?
Something else I am a little confused about is when does DFSR start being used? Do the old servers have to be offline first?

How to migrate the datasource from Bea 8.1 to Bea 10

Hi,
I have to migrate an application from bea 8.1 to 10.
the configuration in 8.1 is as follow : (config.xml)
<JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
InitialCapacity="10" KeepXAConnTillTxComplete="true"
MaxCapacity="150" Name="adiosPool" Password="adios47"
Properties="user=adios47"
RemoveInfectedConnectionsEnabled="false"
ShrinkFrequencySeconds="600" StatementCacheSize="100"
SupportsLocalTransaction="false" Targets="server"
TestConnectionsOnCreate="false" TestConnectionsOnReserve="true"
TestFrequencySeconds="60" TestTableName="SQL SELECT 1 FROM DUAL" URL="jdbc:oracle:thin:@AXHE0.application.hvb.de:1521:AXHE0"/>
<JDBCTxDataSource JNDIName="weblogic.jdbc.jts.adiosPool"
Name="adiosPool" PoolName="adiosPool" Targets="server"/>
and that is my new configuration : (config.xml)
<jdbc-system-resource>
<name>adiosPool</name>
<descriptor-file-name>jdbc/adiosPool-0758-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
jdbc/adiosPool-0758-jdbc.xml :
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>adiosPool</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@AXHE0.application.hvb.de:1521:AXHE0</url>
<driver-name>oracle.jdbc.OracleDriver</driver-name>
<properties>
<property>
<name>user</name>
<value>adios47</value>
</property>
<property>
<name>portNumber</name>
<value>1521</value>
</property>
<property>
<name>SID</name>
<value>HVAEE0</value>
</property>
<property>
<name>serverName</name>
<value>AXHE0.application.hvb.de</value>
</property>
</properties>
<password-encrypted>{3DES}PMWtUXqoHT8=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>weblogic.jdbc.jts.adiosPool</jndi-name>
<global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
but when I start the server I get the following exception :
START SERVER
javax.naming.NameNotFoundException: While trying to lookup 'weblogic.jdbc.jts.adiosPool' didn't find subcontext 'jdbc'. Resolved 'weblogic'; remaining name
'jdbc/jts/adiosPool'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:246)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:213)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
what's wrong ?
Thanks for your ideas

Hi,
This is realated to Upgrading your domain.You can upgrade your domain from bea weblogic8.1SP4 to Bea weblogic 10.You need to use the upgrade tool from bea weblogic platform10.You can start the Upgrade wizard tool from Windows Start->All Programs->BEA Products->Tools->DomianUpgradeWizard.The tool will take you to upgrade the domain automatically.Once you have upgraded the domian everything(database connection pools,users,groups,any other resources) in 8.1 domian will be changed to 10.
Bea Support Complete upgradation of Application as well as application data from 8.1 to 9.2 or 10.0
Thanks
Bishnu
Regards
Bishnu

I recently bought a MacBook Air. I migrated the info from my old MacBook to the new Air. None of my contacts migrated. I still have them on my old Macbook, Ipad and iPhone. How do I get them to the new Air?

I recently bought a MacBook Air. I migrated the info from my old MacBook to the new Air. None of my contacts migrated. I still have them on my old Macbook, Ipad and iPhone. How do I get them to the new Air?

You can copy the iWeb application from the desktop machine to your new MBA. But if it's iWeb 2 it won't work with Mavericks or Mt. Lion. Also copy the Domain.sites file from the desktop to your MBA as that's the file with your webstite files in it.
Happy New Year

Migrating KMS Services from Server 2003 Servers to Server 2012 R2

We have two Windows Server 2003 boxes that a previous administrator had setup as our KMS Servers.
These servers appear to be activating Office 2010, Windows 7, and Windows Server 2008R2 and 2003
I can see these activations taking place in the KMS logs on each server.
The question is what are the steps that we need to take to get the KMS Services migrated to Server 2012 without causing any activation issues in the current environment? I've be unable to come up with the proper order of operations from researching
blogs and I'm just not sure how to get where I need to go, what keys to use etc.
Since this was setup by a previous administrator, there is no documentation on what was done, what keys were used etc.
KMS Server 1:
slmgr /dlv
Name: Office(TM) 14, ProPlusKMSHost edition (Partial Product Key C6PWX)
Description: Office(TM) 14 KMS, VOLUME_KMS channel
Name: Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel (Partial Product Key VX348)
KMS Server 2:
slmgr /dlv
Name: Office(TM) 14, ProPlusKMSHost edition (Partial Product Key 3T9QW)
Description: Office(TM) 14 KMS, VOLUME_KMS channel
Name: Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description: Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel (Partial Product Key TT78P)
Of Note, we are a Microsoft Software Assurance customer and have Volume Licensing
In Summary, I would like to understand how to move my KMS Services to a new 2012 Server(s) and decommission the old 2003 boxes running KMS without disruption. As a final step I'd also like to be able to activate Windows 8, Server 2012, and Office 2013.

Hi,
If you wanted to slowly transition and verify... you could stand up new KMS host and make the priority of the SRV record lower so that clients will always connect to new server first and fall back to original box second.
Steps to migrating the KMS:
1. Uninstall the KMS host key first by running the following command:
slmgr -upk
2. Then, install the default kms key by running the following command:
slmgr /ipk [KMS Client Setup Key]
The default KMS client setup keys can be found here:
http://technet.microsoft.com/en-us/library/cc303280.aspx
3. Delete the record from the DNS:
Open DNS console:
Expand _tcp node under the domain.com. There will be a record _VLMCS. Delete this record.
4. The KMS server is uninstalled.
5. To install KMS on a new server, enter:
cscript C:\windows\system32\slmgr.vbs /ipk <KmsKey>
then to activate the KMS host, enter:
cscript C:\windows\system32\slmgr.vbs /ato
6. After activation is complete, restart the Software Licensing Service.
7. Verify that the record is created for the new server in the DNS.
To verify that the KMS host is configured correctly, you can check the KMS count to see if it is increasing. Run slmgr.vbs /dli on the KMS host to obtain the current KMS count. You can also check the Key Management Service log in the Applications and Services
Logs folder for 12290 events, which records activation requests from KMS clients. Each event displays the name of the computer and the time-stamp of an individual activation request.
https://social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another
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]

Process to migrate configuration data from one BW development system to other

Hi SAP Gurus,
We need to migrate configuration data from one BW system DE1 to DE2.. Both systems are SAP net weaver 7.3.
DE1 is BW pre-production system and DE2 is BW DEV.
No transactional data required.
Please share a document if available.
Kindly, let me know the procedure for Remote Client copy or client export/import with steps.
Also let me know the pre-requisite for these activities.
Thanks,
Avadhesh Sharma
+91 8095226536

Hi,
Remote Client Copy (SCC9)
Remote client copy is performed in rare situation. When the client copy is done
between two different SAP systems, the copy is called remote client copy.
Before remote client copy is performed, a RFC connection must be set between those
systems using SM59.
1. Check RFC connection is working fine between two systems you want to perform
remote client copy using SM59
2. create client in the target system you want to copy the client
3. login to target client using user SAP* and password PASS
4. execute tcode SCC9 and select the RFC for the source system
5. select the profile you want to copy like SAP_ALL
6. select source client number you want to copy
7. Select source client master data , mostly it is the same client number
8. Now click on schedule as background job.
9. Leave the background server field blank.
10. Click schedule.
11. Select Immediate from next screen.
12. Save the screen.
13. Client copy is scheduled now as a background job and client copy process started.
14. The progress can be monitored using tcode SCC3
Client Export/Import
A client transport consists of two steps:
First a client export extracts client data from the source client
to files at the operating system level. Then the data is imported
from the operating system files into the target client.
To perform a client export, follow these steps:
1. Log on to the source client. From the SAP initial screen,
choose transaction SCC8 (Client Export). Select the data to
be copied using a profile.
2. Indicate the target system to which the client will be copied.
The target system must be defined in TMS as part of the
transport domain.
3. Begin the client export. Because copying is a lengthy
process, use scheduled background processing.
Do not run any other client copy tool before the
data export is finished.
This export process will generate up to three data files at the
operating system level:
• RO< number >: this file contains cross-client data
• RT< number >: this file contains client-specific data
• RX< number >: this file contains SAPscript texts
Depending on the type of data selected through the client
transport profile, the client copy command files added to the
buffer of the target system are as follows:
• <S-SID>KO<number>: this file is for cross-client data
• <S-SID>KT<number>: this file is for client-specific data
• <S-SID>KX<number>: this file is SAPscript texts
The client export change requests are not imported when an
Import all takes place. Therefore, you must import these requests into the target client
using TMS. Choose one of the transport requests of the client transport in the Transport
Management System (TMS). The other transport requests belonging to this client
transport are then automatically added in the correct order.
After the import process has completed, post-import activities are required for object
generation steps. After completing the import, log on to the target client. From the SAP
systems initial screen, choose transaction SCC7
Regards,
Chandu

Help in strategy for Migrating to MPLS from PRN cloud Same provider

Dear,
We are planning to migrate to MPLS from PRN using same provider, I have about 12 sites to migrate, new circuits have been provisioned and new routers are ready to be shipped to each site for installation.
Now, I am facing a dilemma, briefly speaking with provider they tell me that we can migrate a site a time no problem here, then next day they tell me it needs to be a hot cut over migration how can this be? so going back and forth and tayloring routers configurations I literally stopped, would like ask for assistance and your opinion on how to go about such migration to tentatively lock into a solid strategy.
Any documents out there you can point me to or experience in such migration will be appreciated.
All of our sites currently connect to PRN cloud including HQ, running OSPF multiple areas, at a glance I was thinking the provider would somehow bridge the two clouds so that I could build a parallel infrastructure and migrate branch offices one at a time but I am still unclear on how to proceed, I will be speaking with the provider more extensively in the next few days but any guidance will be appreciated.
Best Regards

Henry, thanks for those links and help.
Would like to share what I have done which seems so far to be working properly, so that if any one comes accross they get an idea.
It turned out our RPN/MPLS provider cannot or don't want to somehow cross connect the two clouds, so I was forced to do the cross connect at my end begining with two sites, I have setup what I had in mind, for each of the two targeted sites I have installed a new 3845 router with new DS3 link to MPLS cloud and created a cross connect to a 6509_switch_router that is connected under the PRN infrastructure. The 3845 was configured as a virtual link for ospf, all good here so far the 3845 joing ospf domain and received routing table from from PRN side. The next site had also new router and new circuit for the MPLS side, at this second site I brough down the router connecting to PRN cloud then brought up the new 2811 router which I had preconfigured under the same ospf domain and received routing table from the 3845 router DS3 MPLS link. We will let it run for a week to allow to troubleshoot or spod any issues before proceeding to migrate more sites.
Rgds
Jorge

Migrated domain replication from FRS to DFSR. Domain query

Similar Messages

Maybe you are looking for