Migrating Netscape Directory Server 4.1 to a new server

Hi,
In the current production environment, we are using Netscape Directory Server 4.1 as the authentication with Siebel CRM system. The server hardware is old and there is a need to refresh the server. As Netscape Directory Server is the only supported/ certified LDAP with embedded functionalities in Siebel Financial Services 6.0.2.300, we are planning to upgrade only the server hardware and migrate all the user information from old server and the new one, with Netscape Directory Server 4.1 remained.
I have studied the Netscape Directory Server 4.1 Deployment Guide and gone through the migration procedures, looks like the procedures are only applicable for migrating Netscape Directory Server to a newer version. There are no specific procedures mentioned for migrating Netscape Directory Server to the new server hardware with the same directory server version.
I am seeking for detailed procedures of migrating Netscape Directory Server 4.1 to a new server hardware with the same directory server. Anyone has done this migration before? I thank you in advance for your valuable feedback.
Sincerely,
Julie

Luckily, I have the technical documentation in hand, which contains all the configuration of the current server. So I need to use "db2ldif" to export the data. I am currently testing on the migration by following these steps:
1. Install the new server.
2. Stop the Netscape Directory Server and Netscape Administration Server services in old server.
3. Copy the slapd-<server_name> folder from old server to a temp location of new server.
4. Take the old server offline.
5. Configure new server to have the exact configuration as the old server.
6. Backup the existing slapd-<server_name> folder in new server, copy the slapd-<server_name> folder from the temp location to C:\Netscape\Server4 directory of new server.
7. Start the Netscape Directory Server and Netscape Administration Server services in new server.
Will try out your suggested method. Thank you so much for your feedback.
Regards,
Julie

Similar Messages

Migrating CA but CA role was already on new server. Whats the worst that can happen?

Here's a little background for this migration.
Old environment was SBS 2008. Everything baked into one server.
New environment we are migrating to is Server 2012 R2. Will have 8 different 2012 r2 VMs varied by roles. Since this is a small network we are putting the CA on the DC (Called NewDC1).
NewDC1 was configured to mirror the old servers Active Directory, etc. BUT NewDC1 when installed was given the AD CS role as well. From everything I've read it says to backup all settings on the old CA, decommission the old server then install the ADCS
role on the new one and restore the backed up files.
BUT since we already have the ADCS role on the new DC. Should I go ahead and uninstall it. Proceed with the steps to backup and uninstall the exchange server role on the old(not decommission the server since we still need it up to decommission the dc correctly).
Then re-install the role on the new server? Also what issue would you run into with the server not being the same name since that's not even a option?

Is the role installed and ADCS configured as a CA on the new server? In 2012, the role install and configuration process are broken into two separate phases. So if its just installed and not configured, then there's no issue. If however its already been
configured as a CA and it has issued certificates, then anything you have issued from it will be invalidated after the migration.
For the migration itself, since you are renaming the computer that the CA is running on you DEFINITELY want to review the migration process - http://technet.microsoft.com/en-us/library/ee126170(v=WS.10).aspx. There are several steps you will need to
perform otherwise the CA will not work properly on the destination server.
Lastly, it is NEVER recommended to put the CA on a DC. Too hard to migrate or manage the domain, let alone security issues. I would recommend putting it on a dedicated member server, or if you must, at least one that isnt a DC.
Mark B. Cooper, President and Founder of PKI Solutions Inc., former Microsoft Senior Engineer and subject matter expert for Microsoft Active Directory Certificate Services (ADCS). Known as “The PKI Guy” at Microsoft for 10 years.

Migrate Server 2008 Certificate Authority To New Server Different Host Name?

Our internal CA is installed on one of our Exchange servers. Exchange is being migrated from 2010 to 2013, so all current Exchange servers will decommissioned and replaced with new new Hyper-V VMs with either Server 2008 R2 or 2012 R2 OS. The old VM
containing Exchange 2010 and the current CA will go away since we cannot afford to use the server resources and use up the required Windows license to keep that server running doing nothing but acting as a CA.
So, we will either need to move the CA to the new replacement Exchange 2013 server or some other existing server that's being used for something else (maybe one of the domain controllers).
What is the best way to handle this? I don't think the migration from Exchange 2010 to 2013 allows for reusing the same host name on the replacement server and if we move the CA to another existing server, it will also be on a server with a new host
name anyways.
Can we migrate the CA to a new server with a different host name?
What about reissuing all the active certificates from the current server to replace them with new certificates from the new server and then decommissioning the original CA? Can this be automated in some way?
Which way is best and how would it be done?

When following the instructions in the guide, I would also consider to switch to new "sanitized" URLs in certificates (CDP and AIA) in case you had used the default URLs now. That's what I did this when migrating W2K3 CAs (with default URLs) to W2K8 R2.
Per default, the LDAP and HTTP URLs point to the CA server itself (HTTP) or to an LDAP objects that has the same name as the current server.
Migrating to a new server, you need to make sure that CRLs will still be published to the old locations - thus the new CA server would write to the LDAP object that corresponded to the old server, and HTTP might be fixed by redirecting the DNS record. (Make
sure this is documented so that nobody thinks it might be a good idea to delete the old object as it "references a server that does not exist anymore".)
As you have to fiddle with URLs anyway, I would then add new URLs having neutral names - that is URLs not including the name of the CA server. The new CA instance would then 1) publish to the old locations but not add these to certificates anymore and 2)
publish to new sanitized locations and add them to CDP and AIA URLs.
Elke

Migration from XI R2 to Xi R3 and new server box

Hi,
We are planning to migrate to a new server and on that new server, we will install BO XI R3. We have the following issues:
1. All our users have bookmarked the XI R2 address in their browser. How can we transparently forward them to the new server. Can we do it with DNS forwarding?
2. Even we can forward to the XI R3 login page, but how can we keep running our existing Xcelsius Dashboards. The Xcelsius dashboards get refreshed using live office and the live office model points to XI R2 reports. Do we need to update the model for each of the dashboards to point to the new server?
Please let us know if anyone has any suggestion/experience.
Regards,
Tanveer.

My suggestion/experience is you will want to have access to both XIR2 and 3.0 during the migration.
A migration is one of the more complicated tasks and there could be unforseen obstacles.
In theory you should be able to migrate most or all of your XIR2 to 3.0 and then give out a new link to allow others to test. At the same time you leave XIR2 and the old links available in case issues arise you will have a backup.
Live office should be able to be redirected to 3.0 there is a legacy support built in for this (dswsbobje).
The final goal of course is to migrate everything to 3.0 and stop using the XIR2
There are many consultants both within BO/and 3rd party that can help plan a migration.
You should also have the support of the BO deployment team if migration issues should arrise.
Regards,
Tim

Migration process...can't login to new server

Hello all,
I am on page 30 of the migration process where I need to login into the new
server running the NSMEngine. I put in a username and password, like I had
before...and it just hangs.
I read where it said that I may have to be a member of the NSMAdmins
group...there isn't any such group in eDirectory. I have migrated my
policies over and don't want to remove or reinstall anything for fear of
losing my policies.
Any thoughts?
Tom

Tom,
I need more information if I am going to be of assistance.
I need to know what version and platform your running.
thanks,
NSM Development
On 8/3/2011 1:35 PM, Tom Hafemann wrote:
> Hello all,
>
> I am on page 30 of the migration process where I need to login into the new
> server running the NSMEngine. I put in a username and password, like I had
> before...and it just hangs.
>
> I read where it said that I may have to be a member of the NSMAdmins
> group...there isn't any such group in eDirectory. I have migrated my
> policies over and don't want to remove or reinstall anything for fear of
> losing my policies.
>
> Any thoughts?
>
> Tom
>
>
>

Move DPM Server and Disk Data to New Server

What would be the best way to move my current DPM 2012 R2 to a completely new server with all new disks for storage. The data disk are not locally attached storage, but drives physically in the new server and old server. I read the article about moving
the database but am not sure about the migration of the data. How do I get the data from the old server to the new server when not using an external drive array.
Thanks

What would be the best way to move my current DPM 2012 R2 to a completely new server with all new disks for storage. The data disk are not locally attached storage, but drives physically in the new server and old server. I read the article about moving
the database but am not sure about the migration of the data. How do I get the data from the old server to the new server when not using an external drive array.
Thanks
Hi,
On your new server get DPM installed, make sure your disks with your replica's from the old server are in the new server, restore the DPM DB and then run dpmsync. Once DPM is operational you can move the data to the new disks. You can use a GUI tool by Michael
Seidl to move the replicas to the new disks. Here is the link:
https://gallery.technet.microsoft.com/Migrate-DPM-Disk-or-dea8d4e9
My Blog | www.buchatech.com | www.systemcenterportal.com
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion
in a test environment before implementing!

SCSM 2012 R2: Error in DW server after moving workflows to new server

Hi
We have installed a new management server and moved to workflows to the new server, and all looks like it works ok. Then we have followed this to remove the old managment server:
http://marcelzehner.ch/2012/08/01/dealing-with-multiple-management-servers-33-decommission-old-management-servers/
tBut in the data warehouse Operations Managerlog we see: Error 33546 MP Sync failed to connect to Data Access on the machine <name of old managment server>.
Someone know how to fix this?
Please advice
jon

Hi,
You may refer to the below links to unregister the DW by using command Unregister-SCDWSource:
http://technet.microsoft.com/en-us/library/hh541728(v=sc.20).aspx
In addition, here is a blog to troubleshoot data warehouse issue:
http://blogs.msdn.com/b/scplat/archive/2010/06/07/troubleshooting-the-data-warehouse-an-overview.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Use unused server as share point server after move databases to new server

HI,
we have a single server share point farm (ServerApp01) for Intranet and it connects to a SQL SERVER 2008 R2 database server (Server02),
and now we moved all sharepoint databases and content dbs to new sql server in different server (ServerSQLNew).
using sqlalias we point to new SQLSERVER 2012 Instance in this new server.
- now the old sql server (Server02), is not in the sharepoint farm
- now can i add this server in intranet farm and use this old server (Server02) as wfe server ?
here my doubt is when i open cliconfg.exe i saw that sharepoint server pointing to this old server name (Server02),
after i will join this server to existing farm is any issues?
adil

hi
i already turned off sql server instance in old sql server in my case in Server02.
In share
point Server (ServerApp01) i opened cliconfg.exe and add sqlaliases to point to new sql server.
If i rename server02 server or rebuild
the server with a clean OS install still Sharepoint Farm works right?
below is the scenario of sqlalias in sharepointserver (serverapp01)
adil

Migrate Active Directory 2003 to 2012 R2 and Exchange Server 2007 to 2013.

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Md. Ramin Hossain

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Domain. For Exchange installation and upgrading to 2013, you need to make sure that your domain controllers can understand attributes of exchange 2013. Besides if you have DC/Exch on the same server which is 2003 is not supported. Because Windows Server
2003 is not supported.
Migrate your domain to at least 2008 R2 and then proceed with Exchange 2013.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Migration from 10.5.8 in PPC to new server on 10.6.x

Hi,
Currently running 10.5.8 server on a ppc Mac. Looking, at moving to 10.6.x which will thus require new hardware.
Problem is the existing server has a valid externally signed SSL cert. for Web and email and is the domain master for the OD.
If this was a desktop I'd boot the existing box up in target mode and then migrate then upgrade, but I get the feeling the cert. and the Open Directory suff is going to really object to that.
Anyone go any thoughts on how easy this is going to be? I'm guessing new cert. will be required, then moving the clients to new mail server......

To start programming, you can use Mac OS X 10.5.8 and an old Xcode version if you don't want to upgrade now. With this, you will get a first look into the OS X and iPhone OS environment.
However, respecting to iOS programming, I recommend you to upgrade to, at least, Mountain Lion if you can. OS X Mountain Lion needs a Late 2008 Aluminum MacBook or an Early 2009 MacBook, so if you haven't got one of them, you can't upgrade to Mountain Lion.
First, buy Snow Leopard > http://store.apple.com/us/product/MC573Z/A/mac-os-x-106-snow-leopard# Make a backup of your files, insert the DVD and upgrade. After upgrading, open  > Software Update, and install 10.6.8.
Now, if you want, you can upgrade to Lion, if your computer isn't compatible with Mountain Lion. Lion will allow you to use the most recent Xcode version, so you can have a look at programming for the most recent iOS version, which is really useful because you can learn how to create apps for the new iOS 6 features, and if you are a registered developer, you can get access to iOS 7 beta and prepare your apps

Migrating existing portable homes to new server

aside from moving the homedir data from the old server to the new, there seem to be at least a few issues with migrating existing portable home accounts to a new server:
1. some of users' account details, like GeneratedUID, authentication authority, kerberos principals, OriginalNFSHomeDirectory, are different, while others (name, shortname, UID, GID, etc.) remain the same.
2. home directory (OriginalNFSHomeDirectory, etc.) point to the old server.
3. there's data on local machines that we don't sync back to the server, so we can't just blow away the existing local accounts and start fresh.
the quickest way to migrate these users to the new server (with all the same shortnames and UIDs, etc.) seems to be to remove the local cached accounts (leaving the home folders) and have them recreate new PHDs on login, syncing things back down to the original home folder. i'm guess this won't involve much syncing, it's all the same data, essentially.
the other way i can see resolving this is to replace the account attributes for each client to match what they should be when pointed to the new server. this would involve scripting the process for reliability and not moving any data or deleting accounts, but it will take more testing on my part.
what do you think? can you think of better ways to accomplish this task?
summary: what's the best way to move existing portable home accounts bound to "Server A" to "Server B," while maintaining data and portable homes pointed to the new server and storage?
thanks.

that createmobileaccount syntax was wrong. i guess you don't need the -t option and can instead specify the whole path to the user's home. it seems to work well enough, creating a portable home with no default sync settings -- basically manual. for my needs that's fine. the sync settings are managed via mcx anyway.
here's an updated version of the standalone script. i realized just now the script assumes the diradmin usernames and passwords are the same between servers. if that's not the case, you can hard code it or add a couple of variables. since they're just taken in order on stdin, add them in order. i should also add a function to interactively ask for the passwords with stty -echo to avoid having the passes logged in command history or allowing the script to curl the pass from another file on a web server or something. for now, this seems to work for my purposes. edit as you see fit.
#!/bin/bash
# nate@tsp, 3/4/10: initial version
# 3/5/10: added prettier heredoc usage statement, variables, further tested
# todo: add function to add user to local admin group, as needed. this shouldn't be required in most environments.
# todo: convert some of these one-liners to functions for better modular use; make it "smarter"
# todo: convert the whole thing to ruby for practice
# automates the process of unbinding from the old OD server, binding to the new, removing the existing local user, adding it back, and other bits
# there are no "smarts" in this script, so use carefully
# variables
diradminpass=$1
account=$2
password=$3
oldserver=$4
newserver=$5
mkdadmin=$6 # not used in this version
# if no parameters are passed, display usage, exit
if [ ! -n "$5" ] ; then
cat<<endofnote
usage: you must include at least 5 arguments (6th isn't used right now)
run with `basename $0`
1. [directory admin password]
2. [shortname of account to change]
3. [account password, which should be the default 'xxxxxxxx' on the new server]
4. [name of old server]
5. [name of new server]
6. [yes or no to make this account a local admin - optional and not used now]
ex: `basename $0` diradminpass jbrown password oldserver newserver yes
endofnote
exit 1
fi
# if you're running this as root or with sudo, proceed; otherwise, quit it!
if [ $(whoami) = "root" ]; then
echo "you're root. let's proceed..."
# delete the user in question from the local directory store
echo "deleting local account: $account"
dscl . -delete /users/$account
# remove the old od config
echo "removing the old OD bind..."
dsconfigldap -v -r $oldserver -c $HOSTNAME -u diradmin -p $diradminpass
# remove the old server from the search and contacts paths
echo "removing the old search paths..."
dscl /Search -delete / CSPSearchPath /LDAPv3/$oldserver
dscl /Search/Contacts -delete / CSPSearchPath /LDAPv3/$oldserver
# add the new one
echo "adding the new OD bind..."
dsconfigldap -v -f -a $newserver -n $newserver -c $HOSTNAME -u diradmin -p $diradminpass
# create and add the new ldap node to the search policy
echo "adding the new search paths..."
dscl -q localhost -create /Search SearchPolicy dsAttrTypeStandard:CSPSearchPath
dscl -q localhost -merge /Search CSPSearchPath /LDAPv3/$newserver
# create and add the new ldap node for contacts lookups
dscl -q localhost -create /Contact SearchPolicy dsAttrTypeStandard:CSPSearchPath
dscl -q localhost -merge /Contact CSPSearchPath /LDAPv3/$newserver
# give directoryservice a kick to point it to the new server
echo "killing directoryservice and waiting for 20 seconds..."
killall DirectoryService
# rest a bit to ensure everything settled down
sleep 20
# optional: lookup the $account you deleted as the first step to ensure it exists in the new directory
echo "this id lookup should return details because it exists in the new OD:"
id odtestor
echo "this id lookup should fail because it doesn't exist in the old OD:"
id odtestor
# check the search path to ensure it looks like you need
echo "verify the new OD server is in the search path:"
dscl /Search -read / CSPSearchPath
# optional: create a mobile account on the local machine with various options set.
echo "creating a portable home for the user..."
/System/Library/CoreServices/ManagedClient.app/Contents/Resources/createmobileaccount -n $account -v -p $password -h /Users/$account -S -u afp://$newserver/homes/$account
killall DirectoryService
cat<<endofnote
you should be ready to login with this account now.
if you have trouble, revert the process by re-running with the old and new server names
(and diradmin passwords, if they're different) reversed.
endofnote
else
echo "you're not root or an admin. please re-run the script as an admin or via sudo."
exit
fi
exit 0

Migrate WSUS server from 2003x86 to 2008x64, new hardware, use same name and IP address?

Searching through the WSUS forums and reading the TechNET migration documentation, I have bits and pieces of information to make this a smooth transition...I think. I have a plan in mind but
would like the communities input on what I am thinking before moving forward and having it blowup in my face :). <o:p></o:p>
I have the following currently:<o:p></o:p>
A single WSUS 3.0 SP2 server, running on Server Win2003x86, using the default WID (susdb.mdf) on the same server. I have SQL 2005 Express installed on this server as well for other services
but this has no bearing on the WID correct?<o:p></o:p>
What I would like to do:<o:p></o:p>
I have a new server (a much better one) that I would like to move WSUS on to, that will be running Server Win2008x64 (I have to setup first). <o:p></o:p>
Steps that I would like to follow:<o:p></o:p>
1. I will go through and setup this new server with all M$ updates etc... under a new name (ex. wsusnew) and DHCP acquired IP address and then power it down. <o:p></o:p>
2. Get on my current WSUS server and backup all current WSUS settings, groups, DB etc... to a network location for temporary storage. Then power it down.<o:p></o:p>
3. Delete the current WSUS server computer object in AD, DNS entry I will leave because my intension is to give the same IP address to the new WSUS server.<o:p></o:p>
4. Start the new server, static assign the IP address from the old WSUS server to this new server and then change the name of (wsusnew) to the old servers name, which should be ok sense I deleted
the AD object in step 3.<o:p></o:p>
5. After the obvious restart, the new server will have the same name and IP address as the old server. <o:p></o:p>
6. Now that the new server is up (with same settings name/IP as old server), I will then go through and install the WSUS role on the server and restore my WSUS information.<o:p></o:p>
Questions:<o:p></o:p>
1. Step 2 above, is it possible to do this, without making replica servers? I kept reading about this as I was researching doing this, I would rather just copy the DB and folders and simply
put them in-place on the new server.<o:p></o:p>
2. Step 6 above, restoring of the data, what is the proper way to do this in the scenarioI described? <o:p></o:p>
Thank you to anyone who can provide me some information.
Jeff

Thank you for the reply, I will follow and let you know. Proabably be next week sometime before I'm able to try though. So look for a reponse then. Thank you again.
Jeff
OR...
You can use the much more simple, much more reliable, and much more proven method of:
Install new server as a replica of the old.
Replicate.
Configure new server as upstream server.
Point clients to new server.
Turn off old server after all clients have redirected to the new server.
For everybody that has tried the backup/restore the database procedure described above, they have encounted complications of one form or another.
WSUS has a built-in and fully supported comprehensive replication capbility. use it! :-)
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Migrating to new server: advice! :)

Hi!
My current GroupWise 2012 SP2 server is a SuSE 10 SP4 and I need to migrate to a new server!
I currently have 5% disk space left and have ordered additional drives, but while I'm going through the hassle and word is Windemere is not going to be supported on SuSE 10, I've decided to set-up and configure a new server.
This is my plan (this is my first migration) so any suggestions, advice, LOOKOUT FORs, would be welcome with open arms!
The current GroupWise server is a virtual machine on XenServer 6.1 with a NAS attached.
After I install the addition drives, here is my plan of attack:
1. Start up a new SuSE 11 SP2 server.
Notes: The old GroupWise server had a 20 GB disk allocated: 502 MB for /boot and 17.4 GB for / and 2.0 swap
GroupWise files are mounted at /var/opt/novell/groupwise with a 750 GB allocation (it's 83 Linux native).
I think I will double that (40 GB allocation) for room to grow.
Question: What would you recommend LVM or NSS for the partition that will hold GroupWise?
(I will have about 2 TB to work with).
2. Install GroupWise on the new server with the same po/domain name as 'old' server?
3. Install eDirectory on the new server and bring it into a new tree.
4. Perform a Gwava Reload migration.
5. Shutdown eDirectory on 'old' server, backup and restore on new server, then shutdown old server, reboot new server after modifying server name & IP to match old server.
6. Run DSRepair to insure new server is in sync.?
Comments welcome! Stan

Maybe you can do the follow, if you have a small downtime.
1 .Stop GW, make a "chkconfig grpwise off", change IP of the server, reboot and configure the old IP as a secondary(with yast). Then you can start GW again(and "chkconfig grpwise on)".
2. Install a new server with a new name and new IP in the tree.
3. Install the GW-Agents on the new server and copy the config-files (*.poa,*.mta, web?, gwia?, /etc/opt/novell/...gwha.conf) from the old server, and "chkconfig grpwise off"
4. In XEN you can expand the 750GB VOL and then the ext3 or you create a new VOL in XEN and mount it on the same place (/var/opt/novell/groupwise) BACKUP before expand !!
5. If you have a new VOL make simply a rsync to the new VOL, online for the first time
6. Online-Rsync(with delete-option) you can make ever day to see the consumed time, you can use also dbcopy, but this didnt delete old files
7. On Day X you stop GW on old server, make a final rsync (or dbcopy, if you like)
8. remove secondary IP from old server and configure this IP as a secondary to the new server.
9. start GW (if you use gwmonitor its easy to configure it new with the install of GW)
Similar "IP-mechanism" use a GW-Cluster.
In XEN you can make (or you have) a separate network to check this after the first rsync. Switch the server to this network, give the seconday IP and start GW and check the gw-logs and/or start GW with X-Window, if you have runlevel 5 or xming.
Because you have today > 750GB you should think about a second Postoffice, because the handling of big volumes(Backup, Snapshot,...)
That you can make after moving to the new server. Simply build a 2. GW-Server, create a second PO with C1 (or you wait to windermere ??) and move some user.
A Client with the old IP that moved on the new PO is automatically redirected.
Heiko

Migrate to New Server

OES 11 SP2 on an older PE2850 that does not support virtualization!! This existing OES 11 install runs eDir, iFolder, LUM, and imanager (all installed from the disc). We need to migrate off the existing server, replace it with a new server and then migrate back to new server. Can someone point me to a document or instructions on how to do this?

Originally Posted by mrosen
Willem,
Am 14.03.2015 um 22:36 schrieb magic31:
>
> Hi,
>
> carnold6;2349684 Wrote:
>> ...This existing OES 11 install runs eDir, iFolder, LUM, and imanager
>> (all installed from the disc). We need to migrate off the existing
>> server, replace it with a new server and then migrate back to new
>> server.
>
> I'm curious why you are needing to do this (as you are already running
> OES 11 and you want to migrate back)?
Yeah, good question. I understand heneeds to migrate to new hardware,
but why back and forth is a good question. I wonder if there's a SAN
involved which could make it allso much easier..
Yes, need to migrate to new hardware (server) as our current poweredge CPU's do not support virtualization and as i understand it, you can not upgrade from non-virtualization CPU's to CPU's that support virtualization on this poweredge. The reason i say back and forth is because we do not have the new hardware yet. We do have a system that we can virtualize SLES11 on while waiting for the funds and waiting for the new hardware to get here.

Migrating current mobile user accounts from one OS X Server to another

I have not been able to find ANY answers to my situlaton.
I have a small office that currently has a Mac Server 10.4.11 server running that has many "mobile user" accounts setup. This was done because we have so many mobile users coming in and out of the office. When the user comes back they sync their home directory witht th server here. Works great.
We recently purchased a new Mac Server running 10.7.4. Set it up as the Open Directory Master. I unbind from the old server and bind to the new server. Everything seems to be working just fine except when I go and add a current mobile user to the new server it creates a new user account on the client device (MacBooks) as if the previous user settings didn't exsist. Since they need to be mobile users and not just network users I haven't been able to find a solution to this problem any where.
Is there a way on the client to tell it to use the old user account stored on the MacBook to use with new mobile user connected to the new server?
Or is there an easier way of doing this that I don't know about?
Thanks,
TK

If I understand what you wrote, no. The reason is this. If memory serves... In 10.4.11 accounts were assigned a UID. In 10.7.x, accounts are assigned a UID and a GUID. Most everything relies on the GUID at this point. So, what you have is an account named marysue on the workstation and it is assigned a UID like 1045. Now you created marysue on the Lion server, but you likely did not recreate the UID to match the old server. And thus, the UID value is different but more importantly you now have a GUID value like EC0F9357-8EF2-4D3B-B6F3-2E3016400114, that is associated with the account. So, the user, despite having the same shortname, is different.
In addition, you are working with two different directory systems. 10.4 still used NetInfo (ah, I miss you so). 10.5 and above use DS local flat files, even when bound to an LDAP system.
So, probably the easiest way to do this, provided I understand what you are seeing is the following. Let's assume the following:
You have a mobile account on a workstation for the user maryjoe with a UID of 1034 that came from the 10.4.11 system. You have this account cached. You have a home folder in /Users/maryjoe. You have now bound to the new server which contains a user named maryjoe likely with a UID of something other than 1034 and with a GUID value that likely did not exist in the old directory system, also with the shortname of maryjoe and a home path of /Users/maryjoe.
So when you log in, you are likely being pathed to /Users/maryjoe, but you are seeing a default Dock and no documents because of permissions. My guess is that if you used Terminal to view the Users directory you would see something like this (open Terminal and issue the command ls -l /Users/:
drwxrwxrwt   4 root       wheel 136 Apr 18 21:35 Shared
drwxr-xr-x+ 14 locadmin staff 476 Jan 21 7:42 locadmin
drwxr-xr-x+ 14 1034 staff 476 Mar 21 10:42 maryjoe
Note the folder maryjoe is not owned by maryjoe, it is owned by the UID of maryjoe from the old server.
Ok, so long story short (sorry for the log explanation, especially if you are experiencing something else that I did not get from the post), all you need to do is update the permissions of the home folder. Do this:
1: Log in as the local admin
2: Open Terminal
3: Issue this command:
     sudo chown -R maryjoe /Users/maryjoe
Even with a lot of data in the home folder, this should not take more than a few minutes to complete.
When the command completes, run this command again: ls -l /Users/
You should now see
drwxrwxrwt   4 root       wheel 136 Apr 18 21:35 Shared
drwxr-xr-x+ 14 locadmin staff 476 Jan 21 7:42 locadmin
drwxr-xr-x+ 14 maryjoe staff 476 Mar 21 10:42 maryjoe
Now try logging in as the user. With a little luck I divined the issue and this will have you up and running. Now, I normally will also purge the cached account in /var/db/dslocal/nodes/Default/users/ but that might be a bit daunting. So let's start with the simple process first of ensuring home folder permissions are correct.

Migrating Netscape Directory Server 4.1 to a new server

Similar Messages

Maybe you are looking for