Solaris 8 Cross Server Migration

Hi,
Currently, I have Solaris 8 on both E450 & E250.
I would like to unplug all the HDDs from the above 2 servers & plug it into:
E250 - From E450
E2 - From E250
Is it possible to let it run without modifications/re-generation after migration?
Thanks,
Raymond

Well, since you're using Solaris 8 we can try it with devfsadm from a CDROM boot. 15010 was using drvconfig.
Insert a Solaris 8 CD ( Install or CD 1 of 2)
ok boot cdrom -s
# fsck /dev/rdsk/c0t0d0s0
# mount /dev/dsk/c0t0d0s0 /a
Move path_to_inst
# mv /a/etc/path_to_inst /a/etc/ORIGINAL_PATH_TO_INST
Remove all old device links
# rm /a/dev/rdsk/c*
# rm /a/dev/dsk/c*
#rm /a/dev/rmt/*
# devfsadm -r /a -p /a/etc/path_to_inst
# umount /a
# halt
ok boot -r

Similar Messages

WSUS 3.0 SP2 master server cross-forest migration impacts

    Hello to all, I'm preparing a cross-forest migration and have one WSUS 3.0 SP2 master on source forest placed in root domain. This master has 16 replicas scattered among child source domains. As I plan do migrate member servers using MS
tool named ADMT 3.2 and considering that I will firstly migrate just root domain member servers to target forest, I need to know:
   1- Will WSUS 3.0 SP2 master server work after it's migrated from source to target forest? I mean: can all its replicas still access and donwload the necessary patches from it? Will its configuration be in place (groups, schedules, etc) ?
   2- Should I need to change source domain clients WSUS GPOs to point to the just migrated master server (new FQDN name)?
   3- Is possible to change my just migrated WSUS 3.0 SP2 to be replica from a master server already present on target forest? How this move could affect its existing replicas still present on source forest?
   Suggestion and attention points will be appreciated.
   Regards, EEOC.

1- Will WSUS 3.0 SP2 master server work after it's migrated from source to target forest? I mean: can all its replicas still access and donwload the necessary patches from it? Will its configuration be in place (groups, schedules, etc) ?
Fundamentally yes, as long as the downstream servers are updated to use the new hostname and DNS properly resolves that hostname. NOTE: You cannot "migrate" the WSUS role using ADMT. What is your plan for "migrating" the WSUS upstream server?
2- Should I need to change source domain clients WSUS GPOs to point to the just migrated master server (new FQDN name)?
Probably. Presumably the hostname and IP Address of the server are going to change.
3- Is possible to change my just migrated WSUS 3.0 SP2 to be replica from a master server already present on target forest?
Yes, but that's kind of a cart-before-the-horse move... which brings us back to the original question: How do you plan to "migrate" the upstream server?
How this move could affect its existing replicas still present on source forest?
Well.. it will introduce a three-tier replication hierarchy for starters, which will slow everything down by one or two days. But, really, I wouldn't worry about that because there's no real need to do this.
Suggestion and attention points will be appreciated.
Install a *NEW* WSUS server in the target forest.
Configure it as a replica of the existing master in the source forest.
Replicate.
When the replication is complete, reconfigure it as an Upstream Server and RESET the Product Category and Update Classifications to what they should be.
Synchronize with Microsoft.
When that sync is successful, enabled regular synchronizations.
Configure clients and downstream servers to sync from the new upstream server in the target forest.
When all clients and downstream servers are working with the new server, turn off the old one.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Cross platform migrate repository and oms, gets "EM Key Verification Error"

Hello,
I am trying to cross platform migrate repository and oms from Sun Solaris Sparc 64 bit to Linux x86-64bit.
Environment:
Original repository Oracle 10.2.0.3, OMS 10.2.0.5, Sun Solaris Sparc 64 bit
New repositoy Oracle 10.2.0.3, OMS 10.2.0.5, Linux x86-64bit
Following metalink note:
Subject: How To Move Grid Control Oms & Repository To Another Server
Doc ID: 853293.1
to step 4:
4. Point the new OMS to the new repository
can't get over emkey corrupt issue, gets error:
2009-10-13 14:07:24,570 [AJPRequestHandler-ApplicationServerThread-11] ERROR conn.ConnectionService verifyRepositoryEx.918 - EM Key Verification Error = Em key does not match with repos verifier
2009-10-13 14:07:27,910 [Shutdown] ERROR em.notification unregisterOMS.2573 - Error unregistering: EM Key is Missing java.sql.SQLException: EM Key is Missing
The newly installed additional OMS can only point to the original repository and can't point to the newly migrated repository.
Steps I did:
Install an addition OMS to point to original repository (make sure emkey is in repository)
create a new empty database on new host with a new name (is new name caused problem?)
migrate old repository to new (use export/import)
point new OMS to new repository by modifing emoms.properties
startup oms and gets emkey corrupt error
This metalink note does not help either:
Subject: The Em Key is not configured properly. Run "emctl status emkey" for more details.
Doc ID: 817035.1
I also have a SR open but still have no help from Oracle support. I did make sure the emkey is in the repository before migrate. There may be tricks that I don't know.
Can anyone shed some light on this?
Thank you for your help in advance.
Edited by: user1062137 on Oct 16, 2009 2:14 PM

Hi, I'm having the same issue.
Our original installation was on Windows 32bit with the repository and OMS on the same host. I want to move the repository to a linux 64bit host to make more resource available for everything. The new database is 11.1.0.7 though. As the Grid control release is 10.2.0.5 Oracle Support have confirmed that the 11g database is OK to use.
In the log I see a lot of this:
[AJPRequestHandler-ApplicationServerThread-5] ERROR conn.ConnectionService verifyRepositoryEx.911 - Invalid Connection Pool. ERROR = ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
2009-11-05 18:54:57,254 [AJPRequestHandler-ApplicationServerThread-7] ERROR conn.FGAConnection _setConnContext.326 - java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
2009-11-05 18:54:59,973 [Shutdown] ERROR em.notification unregisterOMS.2573 - Error unregistering: EM Key is Missing
java.sql.SQLException: EM Key is Missing
Unfortunately that package is wrapped so I can't see what privs are required.
The instructions say (simplified here) either datapump or exp/imp to the new database, run some admin scripts, then update the emoms.properties with the new connection information. Thats it - start OMS again and it should work.
Thankfully I can turn the old repository back on while I sift through these logs.

Cross Forest Migration from Exchange 2007 to Exchange 2013

Hi
Could anybody advice me the steps also the pros and cons for below mentioned environment if we are going for the cross forest migration.
Source
Domain - test.local
Active Directory - Windows 2003
Exchange Server - 2007
Target
Domain - test.net
Active Directory - Windows 2012
Exchange Server - 2013
Also if it is possible ,
How could I remove the source environment including the exchange servers. after the migration ?
Regards
Muralee

Hi Oliver ,
Please suggest us.
In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
Source : Exchange 2007 with sp3 ru 10
Target : Exchange 2013 with cu2 ( new environment yet to be created).
Trust : Forest trust in place (two way )
Domain and forest functional level : 2003 in both target and source
Migration Steps :
Step1 :
We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
in the target forest.
Step2:
Then we are going to use ADMT to migrate users SID'S and password .
Step3:
Then we are going to move the mailboxes with New-moverequest
Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
.Is anything needs to be changed please intimate me .
Thanks
S.Nithyanandham
Hey there,
Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Server Migration

I'm having a problem setfing up migration on my Managed Servers on Welbogic 9.2 mp2. First, My problem.
When I try to manually migrate ManagedServer1 from MachineA to MachineB:
Nodemanger shutdowns ManagedServer1
Nodemanager removes the interface with the floating IP (so far so good)
(here is where the problem starts)
Nodemanager brings up the interface back on MachineA
Nodemanager starts ManagesServer1 on MachineA (all this is suppose to happen on MachineB).
This doesn't help me if it migrates it to the same machine!!!
I quick overview of how things are set up.
1) I have two machines, MachineA and MachineB running Solaris 10
2) I have the admin server running on MachineA listening on the static ip of 139 and ManagedServer1 listening on the floating IP of 169 (fyi, don't want give out IP, so I made a number up)
3) I have ManagedServer2 running on MachineB with the floating IP of 170.
4) I created a weblogic user that has ssh trust config between the two machines and has the proper authority to create and bring down an interface.
5) Created 2 Unix machines, Type SSH with the shell command ssh -l legalint -o PasswordAuthentication=no -p %P %H /opt/bea/weblogic92/common/bin/wlscontrol.sh -d %D -n /legalint/mtdom/ndmgr -c -f startManagedWebLogic.sh -s %S %C
6) Network Time Protocal Config is set
7) Lease database schema is created with corresponding data source and has two tables ACTIVE and ACTIVE_MT
8) Server migration progerties configured: cluster datasource is set (In my directions it tells me to leave the Canidate machines blank). Managed servers auto migration set to true and primary and back-up machine set and auto-restart set to true.
Any help is appreciated.
Tom.

The best way to deal with certificates and FQDN's in ZESM is to use commercial issued certificates or from the company's internal CA. Don't use the built-in product self-signed certificates under any reason for production deployments. The reason behind that, is that the internal ZESM certificate has its private key marked as non-exportable. So you'll not be able to export it from one server and move to another.
For the server FQDN, create an A or Alias record in DNS to something like: "zesm.company.com", and point it to the actual ZESM server, that way, once you need to move all users from server, all that you need to do is to import the commercial certificate and point the DNS record to the new server IP Address.
I did a couple of deployments in that way, with no issues.
Hope this helps.
>>>
From: mauro vaccari<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 1/19/2010 7:36 AM
Subject: Server Migration
Hi,
planning the upgrade to the imminent release of ZESM 4.1 we would like
to reinstall the server because it has undergone many installations.
For security reason and for don't stop production we want to install
ZESM 4.1 in a new server with the same ip and name of the actual then we
want try It in a test VLAN.
My question is:
when we want to pass the new server in production or before ZESM
instalation could we migrate the IIS certificate from the old server to
new one? so the client should not be involved.
Thank you for help
mauro_vaccari
mauro_vaccari's Profile: http://forums.novell.com/member.php?userid=16902
View this thread: http://forums.novell.com/showthread.php?t=398639

Cross platform migration from hp unix to sun

Hi
recently we have done cross platform migration from hp unix to sun (10g R2 RAC +ASM). It was a challenging experience to complete the migration in 8 hours downtime for a database of about 2 TB.
I would like to share the experience , so that it would be hepfull to others and i would learn more new techniques for improvement .
source environment:
HP-UX -ITANIUM - 2 node RAC - 10g R2 - Oracle clusterware - ASM - Heavily loaded all the time .
Destination Env:
Sun solaris 10 - 2 node RAC - 10g R2 - Oracle Clusterware - ASM
Total Downtime available : 6 hours.
Steps followed
1. snapshot backup of source database on a intermediate HP-Unix box. (stage area)
2. recover the database and start the rman image backup on to disk in stage area.
3. mount this filesystem locally (Veritas ) on to one of the node in the destination env.
4. Mount this filesystem as NFS on second node using a cross cable between both of them (we can use interconnect VLAN also here)
5. Keep applying the archive logs from source env till the downtime .
5. startup nomount the database , change the datafile names from ASM to RMAN image copy files and mount.
6. start rman convert statements and pump into the already exisitng ASM nodes with parallel sessions as much as possible (with 35 sets (513 datafiles) we were able to pump 2 TB data in 4.5 Hrs) - only system and undo datafiles need a convert statements (platform migration ) others would need a file system to ASM conversion only.
7. alter database open resetlogs in the destination environment.
8. create services manually and start the application.
we were given very less time to decide upon this stategy , By gods grace we were able to complete it .
I got a doubt while we are chalking out this plan .
can we connect to ASM instance remotely and pump data from one ASM to another ASM. It seems it is not possible , just a wild thought.
Let me know if you see any more improvements in this.
Thanks
Naveen samala

can we connect to ASM instance remotely and pump data from one ASM to another ASM. It seems it is not possible , just a wild thought.No. Thats not possible.

OES11 miggui fails on cross-tree migration

Maybe Ramesh will see this:
Doing a cross-tree migration, and choosing to create the trustee users on the destination tree.
This is what the file system log shows for failures:
(oh, the SOURCE server is OES2 SP3)
Code:
2012-01-27 11:22:34,197 INFO - FILESYSTEM:Information:****************Migrating files and/or trustees****************
2012-01-27 11:22:34,197 INFO - FILESYSTEM:mls:Scanning APPS1:Documentation for rights, trustees and quotas using mls
2012-01-27 11:22:34,199 INFO - FILESYSTEM:mls:Executing command: /opt/novell/migration/sbin/mls --source-server 10.10.1.11 --source-path "APPS1:Documentation" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.session" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:33,097 INFO - FILESYSTEM:mls:Successfully scanned trustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Mapping users and groups from APPS1:Documentation to /media/nss/APPS1/Documentation using maptrustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Executing command: /opt/novell/migration/sbin/maptrustees --source-server 10.10.1.11 --destination-ldap-container "o=abc" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.yaml" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:39,153 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,563 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,569 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,553 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,557 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:54,063 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:56,095 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:03,139 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,827 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,832 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,583 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,744 INFO - FILESYSTEM:maptrustees:Successfully mapped trustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Creating users and groups existing on APPS1:Documentation to /media/nss/APPS1/Documentation using migtrustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Executing command: /opt/novell/migration/sbin/migtrustees --destination-server 10.10.1.12 --verbose --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_migtrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.yaml" --progress --progress-interval 1 --destination-unsecure-ldap --destination-ldap-port 389
2012-01-27 11:24:10,035 FATAL - FILESYSTEM:migtrustees:Fatal: Caught exception: syntax error on line 366, col 14: ` givenName: 'Brenda''
2012-01-27 11:24:10,107 ERROR - FILESYSTEM:migtrustees:migtrustees command failed!
2012-01-27 11:24:10,108 INFO - FILESYSTEM:Information:****************End****************
2012-01-27 11:34:05,713 ERROR - FILESYSTEM:volmount.rb:Command to mount source: ruby /opt/novell/migration/sbin/volmount.rb -s 10.10.1.11 -a "cn=admin,o=dec" -c Not Applicable -f "/var/opt/novell/migration/OESSP1-APPS1/fs/mnt/source" -m -t OES20
So I'm not sure if it's the logintime stuff that's making it fail (I see a TID with no update) or the odd part about having a problem with a given name

$(UThe loginallowedtimemap and networkaddressrestriction attributes are stored as double byte encryption encoded strings, which are not read by the current maptrustees script.
For OES11 we have documented the workaround in the Trouble Shoot section 16.7.3 @ http://www.novell.com/documentation/....html#bookinfo
-Ramesh
>>> kjhurni<[email protected]> 01/27/2012 10:26 PM >>>
Maybe Ramesh will see this:
Doing a cross-tree migration, and choosing to create the trustee users
on the destination tree.
This is what the file system log shows for failures:
(oh, the SOURCE server is OES2 SP3)
Code:
2012-01-27 11:22:34,197 INFO - FILESYSTEM:Information:****************Migrating files and/or trustees****************
2012-01-27 11:22:34,197 INFO - FILESYSTEM:mls:Scanning APPS1ocumentation for rights, trustees and quotas using mls
2012-01-27 11:22:34,199 INFO - FILESYSTEM:mls:Executing command: /opt/novell/migration/sbin/mls --source-server 10.10.1.11 --source-path "APPS1ocumentation" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.session" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:33,097 INFO - FILESYSTEM:mls:Successfully scanned trustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Mapping users and groups from APPS1ocumentation to /media/nss/APPS1/Documentation using maptrustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Executing command: /opt/novell/migration/sbin/maptrustees --source-server 10.10.1.11 --destination-ldap-container "o=abc" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.yaml" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:39,153 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,563 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,569 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,553 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,557 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:54,063 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:56,095 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:03,139 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,827 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,832 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,583 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,744 INFO - FILESYSTEM:maptrustees:Successfully mapped trustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Creating users and groups existing on APPS1ocumentation to /media/nss/APPS1/Documentation using migtrustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Executing command: /opt/novell/migration/sbin/migtrustees --destination-server 10.10.1.12 --verbose --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_migtrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.yaml" --progress --progress-interval 1 --destination-unsecure-ldap --destination-ldap-port 389
2012-01-27 11:24:10,035 FATAL - FILESYSTEM:migtrustees:Fatal: Caught exception: syntax error on line 366, col 14: ` givenName: 'Brenda''
2012-01-27 11:24:10,107 ERROR - FILESYSTEM:migtrustees:migtrustees command failed!
2012-01-27 11:24:10,108 INFO - FILESYSTEM:Information:****************End******** ********
2012-01-27 11:34:05,713 ERROR - FILESYSTEM:volmount.rb:Command to mount source: ruby /opt/novell/migration/sbin/volmount.rb -s 10.10.1.11 -a "cn=admin,o=dec" -c Not Applicable -f "/var/opt/novell/migration/OESSP1-APPS1/fs/mnt/source" -m -t OES20
So I'm not sure if it's the logintime stuff that's making it fail (I
see a TID with no update) or the odd part about having a problem with a
given name
The opinions expressed are my own.
Check out my OES2 Guides:
Installing OES2 SP2:
http://www.novell.com/communities/no...allation-guide
Upgrading to OES2 with ID Transfer:
http://www.novell.com/communities/no...r-id-scenarios
GroupWise Migration with OES2 ID Transfer:
http://www.novell.com/communities/no...p2-transfer-id
kjhurni's Profile: http://forums.novell.com/member.php?userid=734
View this thread: http://forums.novell.com/showthread.php?t=451439

Cross platform migration question.

I have a customer that is currently runnning oracle 10g databases on solaris 64 bit operating system on sun m4000 and m5000 hardware. The customer is looking to move to the redhat 6 operating system.
I am wanting to know what method will be available for me to migrate the databases as the endian on the files are different? Will transportable tablespaces work with the different endian?
Thanks.

Hi;
I suggest please also see:
How To Use RMAN CONVERT DATABASE on Source Host for Cross Platform Migration [ID 413586.1]
Master Note For Oracle Database Upgrades and Migrations [ID 1152016.1]
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

Is that possible to do the cross domain migration for AD RMS Services?

Hi guys, recently i am doing a cross domain migration, when i listing out the server, i found the server have AD RMS services which is still active.
but after my migration is complete, it is planned to do the decommission on all the old server
After my checking, i believe the AD RMS have trust establish with a cross site domain already. What i am planning to do is try to do a migration on it.
i have do some research on it an i found "Cross forest Migration of AD RMS document"
what i found in the document, it have mention about
In the event when one cluster running AD RMS is to be discontinued, users may still want to access
previously protected content that was issued a publishing license by that computer. Servers in other clusters can then add the to-be-discontinued server as a trusted publishing domain.
So i was wondering if there is an option for Ad RMS services to select a server or host to discontinued?
The scenario in my head now,
1.Build trust between in my new domain AD RMS with the existing AD RMS. update the certificate between the trusted domain as i mention above with my new domain AD RMS.
but i was wondering if i power down or decommission the server what will happen?
2. the worst case scenario will be decommission the old AD RMS service, and publish the new AD RMS services in new domain, simply build trust with the cross site domain.
any suggestion on this? which case is more workable?
Thanks
Dave

Hi,
I think you may ask in AD RMS forums:
http://social.technet.microsoft.com/Forums/en-US/home?category=rms&filter=alltypes&sort=lastpostdesc
Regards.
Vivian Wang

Cross Forset Migration from sccm 2012 to sccm 2012RS

Hi all,<o:p></o:p>
We have a plan to migrate
sccm 2012 to sccm 2012 R2 on trusted forest (cross forest migration)<o:p></o:p>
Please share possibility...<o:p></o:p>
Thanks, Mariappan Shanmugavel

Possibility for what?
Migration only works from ConfigMgr 2007 SP2 or from the same version of ConfigMgr 2012 thus will not be able to migrate from 2012 to 2012 R2. You will need to upgrade your 2012 site to 2012 R2 first and then perform the migration. The TechNet docs clearly
show this: http://technet.microsoft.com/en-us/library/gg699364.aspx
ANd, as Torsten pointed out, if you are simply planning on moving the existing site server, that isn't supported and won't work either.
Jason | http://blog.configmgrftw.com | @jasonsandys

Cross Plateform Migration:Target Folder not found

Hi All
I am try to use Cross Plateform Migration Fnction to migrate Data to AD file server. and I have perform [Migrate Data and Trustees] to migrate "user to user", but the last step "Validate", it show "Target folder not found "....Ireview all steps I set...indeed I seem not set target file server path.
But I do not which step let me could set Target File Server, By using Policy or which place ? Who could kindly tell me How to set Target File Server path ?
thanks!!
wyldkao

wyld,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

BW Steps before and after R3 server migration

Hi Friends,
We are using ECC6 and BW 3.5.
My client is going for R3 server migration, yes it's just a migration of server and not any upgrade. This server is quite old so migrating to a higher end server.
BASIS will do a system copy during downtime i.e. a homogeneous client copy where they would just copy the DB tables. As per them all data will remain same and only the IP will change i.e. i will have to make a change in R3-BW RFC connection.
I need to know what other pre and post migration steps are involved in this case?
Thanks,
BJ

Hi,
I dont think that there would be any impact on queues etc due to server migration. We flush out data from queues only in cases of upgrade/ patch application etc. because there is a chance that after the upgrade the structure of datasource may change. In that case, any data lying in queue beforehand would get corrupted and cannot be loaded.
in your case, there is no such change going to happen, therefore no need to worry about queues. You can go ahead without worrying about any dataloss due to queues.

Root password fails on auth to Solaris Management Console Server

I've setup Solaris 10 x86 on a VA linux 1220 server, all is good so far except when I try to create additional users. I am logged in as root, and the root password logs in to the CDE, but fails on authentication to Solaris Management Console Server when I try to use any of the management apps like computers and networks or Users. So I'm stalled at the point where I should be configuring the system. I have been very careful about typing in the password exactly as I use it in the login screen, but it never works in the System Management tools for This Computer. The password I'm using is 26 characters long, is it too long? Or is there a step I'm missing?
Thanks,
Brian

One of my famous guesses, but unless you changed the default password algorithm the maximum length of your password is 8 characters, when logging in on the console or desktop, anything typed after those eight characters will be ignored (unless this behaviour changed very recently).
Its possibly that SMC, and its server component WBEM does not ignore the extra characters, which could cause this behavior.
What happens if you try and login to SMC with the root user and only the first eight characters of your password?
Btw, if this was the problem i think there is a way to change the default crypto algorithm to something that supports more characters.
.7/M.

No Solaris Management Console server was available

I just installed solaris 8/07 fully patched the OS using smpatch went to use smc and get No Solaris Management Console server was available error.
# netstat -a | grep 898
localhost.898 *.* 0 0 49152 0 LISTEN
fmri svc:/application/management/wbem:default
name SMC and WBEM Server
enabled true
state online
next_state none
state_time Sat Jan 31 21:01:59 2009
logfile /var/svc/log/application-management-wbem:default.log
restarter svc:/system/svc/restarter:default
contract_id 102
dependency require_all/error svc:/milestone/sysconfig:default (online)
log::
[ Jan 31 21:01:57 Stopping because all processes in service exited. ]
[ Jan 31 21:01:57 Executing stop method ("/lib/svc/method/svc-wbem stop") ]
[ Jan 31 21:01:59 Method "stop" exited with status 0 ]
[ Jan 31 21:01:59 Executing start method ("/lib/svc/method/svc-wbem start") ]
[ Jan 31 21:01:59 Method "start" exited with status 0 ]
I have even uninstalled all packages related to smc reboot, and then reinstalled them from the dvd reboot.
Still won't load so I patched back up.
Any idea?
Thanks
Admin please move or delete this post I have tried and can't find an option to delete.
I'm really sorry I put this in the wrong forum. Center not Console.
Edited by: mark42324 on Jan 31, 2009 6:22 PM

Regarding SMC (not SunMC)..
Note: SMC = Solaris Management Console
SunMC = Sun Management Center (topic of this forum)
Patch 121308-16+ makes WBEM "secure by default."
Customers running Solaris 10 6/06 or prior must modify the client's WBEM
configuration file to allow remote connections after installing patch 121308.
1. Modify the following line in /usr/sadm/lib/smc/policy/smcserver.config:
FROM:
remote.connections=false
TO:
remote.connections=true
2. Stop and restart wbem.
# /etc/init.d/init.wbem stop
# /etc/init.d/init.wbem start
3. Verify that WBEM is now listening for connections to port 898
on all interfaces:
# netstat -an |grep 898
*.898 *.* 0 0 49152 0 LISTEN
In Solaris [TM]10 update 3 (11/06), the startup mechanism for WBEM was changed
from the legacy (rc script) method to the new Service Management Facility (SMF).
To allow remote WBEM connections on Solaris 10 update 3 or later:
# svcadm disable wbem
# svccfg -s wbem setprop options/tcp_listen=true
# svcadm enable wbem

Solaris 8 Cross Server Migration

Similar Messages

Maybe you are looking for