Migrating to a new Messenger server

Our current physical mail server, running both GW and Messenger, is a bit long in the tooth. We've migrated away from GW into a unified Exchange-based system, but the GW server is still active for some archival mailboxes that were not migrated for whatever reason.
Anyhow, I've spun up a new SLES 11.3 VM with the intention of migrating our Messenger services over to it. Originally, my intention was to run the two servers concurrently during a testing phase, but if I am reading the docs correctly, it seems that's not possible. What are my other options? Do I install it to a different tree and move it later?
I was also looking for clarification on LDAP vs eDirectory authentication. Would I be losing anything by choosing LDAP?
Thanks.

Thanks for the reply!
Regarding the LDAP/eDir issue, I'm not looking for AD at all, I just didn't know if it mattered if I hit the tree via true eDir or LDAP, if I'd be missing fields or something.
Also, I'm not concerned about users logging into different servers concurrently, I can't imagine the use case for that, except maybe for failover? Anyhow, I just want to make sure I'm allowed to have more than one Messenger server in the tree, because in the docs, it didn't seem like that was possible. It seemed like if I activated a second server, it would take some of the roles away from the first. It didn't say so specifically, it's just how it looked.
And yeah, our current messenger server has a DNS alias of 'messenger,' I wanted to set up a second as 'messenger2' so that I could set it up for testing and then change the alias when ready to move to production.
Thanks.
Originally Posted by laurabuckley
Hi
As far as I'm aware you can not have users authenticated to two different messenger servers concurrently. You will have to pick either your old server or your new server.
I'd keep your new server in the same tree so that credentials remain the same. We have our Messenger client connect to a DNS name so every time we move it to a new server all we do is update the DNS record.
Ldap/edir all the same with Messenger. It currently can only authenticate via eDirectory. It's on the road map to have AD authentication, I think, but it's some way off.
Shout if I can be of further assistance.
Cheers,

Similar Messages

Embedded font errors after migrating pdfs to new web server

Hi All,
After hundreds of working pdfs were moved to new web server, they produce variations of the "cannot extract the embedded font" (name of font) "some characters may not display or print correctly" error. The first page loads perfectly and the rest never load. All these files open fine when I open local copies in Reader (9.1.3) and Professional (7.1.0).They also open fine when moved to another server. When I delete copies on the server and re-upload using the working copies, the errors persist. Doesn't make sense. I also occasionally get the error "there were problems reading this document (14)".
I was told by the IT department that a possible cause was that the new server environment used fonts installed on the server rather than the local machine to display pdfs. This doesn't make sense to me. I've researched these errors and haven't found anything applicable or that has worked. Any suggestions? Has anyone else expeienced this?
The server is IIS and is running ASP.net. The IT dudes are saying they need to install all the refferenced fonts on the web server but due to the expense of this, they can't.This will nessecitate a really bizzarre and Rube Goldbergesque workaround (that I'm not even going to try to explain here) that I'd really like to avoid. Any suggestions? Are there any Acrobat settings that need to be twekaed?

Hi,
I read the following on another discussion in this forum:
it appears that with the shortkey ctrl+shift+Y you can force the pc to work around the system fonts
Maybe that helps.
Jenny

Migration to a new weblogic server

Hi Iam trying to migration my application from the development to test environment,
For this i have to deploy to the test weblogic environment
for this i am doing the following
1. add the application server connection .
2. add the database details of the test db connection in the AM : business components > Database
3. change the AM : Configuration > manage configuration > change the jdbc soucename to the source name defined on the test env weblogic server.
And then iam deploying the application.
The deployment is going on fine.
But the page is not rendering....
the page structure is
panel header > title
querypanel > VC
table > searcjh results
Only the title of the page is displayed....
i suspect some where i have to missed the db connection setting and its not able to connect to the test db
Could you please suggest.. where all i need to change the db connection details so that it works.
thanks

Hello,
at first you have to verify, whether your DB connection have been set up correctly. You can do this in your administration console by clicking on Services/Data Source on your domain structure tree. First click the Monitoring tab to see whether the connection has tha running state. Then select your data source and switch to the Testing subtab of Monitoring tab. There you should select the radio button and click the "Test Data Soruce" button.
If the connection is verified and working, and the application still not rendering correctly, then take a look into your log file, and post here the error message

Voicemail access issue when migrated to new Domino server

st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
At the current time we have one Domino v7.0.4 server (Win2k with DUC v1.2.3) in production and our clients are running Notes v7.0.4 client with DUC v.1.2.3 installed on them. This setup has been working great in our Unity v5.0(1) environment. We are looking to migrate our users to a newly installed Domino v8.5.1 (Win 2008 x32 DUC v1.2.5) server in the near future but out test users are running into a problem.
When a user gets migrated over to our new Domino server the client can no longer access their voicemail via TUI. During the user migration process we do change the pointer in Unity to their mail file on the new Domino server. When the user logs in they receive "Your messages are available now"
If we migrate the user back to the old v7.0.4 server they can access their voice mail with no issues.
Any feedback you could provide would be great. Thanks!

Hi Kenneth,
Could you clarify what you mean by "During the user migration process we do change the pointer in Unity to their mail file on the new Domino server"? Typically when moving a user's mail file to a new Domino server, Unity should automatically pick up those changes. Are you pehaps creating a new mail file and pointing Domino to it instead of moving it? If that is the case, the new mail file would not have been DUCS enabled, a process it must go through before Unity will be able to access it properly. The only way to force that to happen would be to reimport the user into Unity. If the mail file is properly migrated, however, the mail file should remain DUCS enabled and there would be no need for this.
An easy way to determine whether the user is DUCS enabled is using the DUT tool. It is located on the Unity server under \Commserver\Utilities\Domino\DUT. It will show you a list of all of your users. Compare the values you see in the UCProfile section for a working / non-migrated user to a failing one. You might also want to verify that it lists the updated mail server and mail file for the user.
Also, while I don't think it would cause this particular problem, you should be aware that Server 2008 is not currently a supported platform for DUCS/CsServer 1.2.5, see page 6 in the admin guide:
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/duc/admin/guide/cuducag.pdf
Hope this helps,
Pat

Server 2003 SBS (with Exchange 2003) migrate to new machine Server 2012 Standard (with Exchange 2013)

This is what I have:
A very outdated machine running a small domain, SBS 2003 and Exchange - this is the ONLY server currently.
This is what my boss ordered:
A Dell R210 II machine with Server 2012 Standard (and I downloaded the trial for Exchange 2013).
He wants the old server completely replaced and gone - with everything moved over (including Exchange) to the new machine. The main reason for the upgrade is that not all users can access email on their machines (Macs, new versions of Outlook, etc.)
I have set up a new standalone server before but never migrated one - and I've found that going from SBS2003/Exchange2003 to Server2012/Exchange2013 is not simple in the least.
I thought I could just set up the new server as a DC on the domain and have everything replicated to it from the source server. Then I could decommission the old server. I have been told that 1) I can't upgrade Exchange 2003 to 2013 and 2) that I shouldn't
put Exchange on a DC. What do you do if you only have the one server?

Hi,
Just additional. Please also refer to following threads and article, then check if can help you.
Migrate
SBS 2003 to Windows Server 2012 Standard
Migration
SBS 2003 to Windows Server 2012 Standard
Transition
from Small Business Server to Standard Windows Server
Hope this helps.
Best regards,
Justin Gu

New Mini Server - Can't see volume to migrate from.

I literally just opened my mac mini server (Lion Server) and as usual the setup screens started. Once it said I could migrate a server I proceeded with that option. However there's no volumes that the Mini Server recognizes. I am plugged into the LAN which has our Snow Leopard server, but it doesn't see that.
Is the mini server supposed to be able to see network attached Mac computers or not? Do I need to physically plug our Snow Leopard server into the mini? This is stange. Just opened a new machine and can't even get past the setup. Is there a server migration assistant?

I have not tried migrating a server in this way, but I would imagine it would be a similar process as to how Migration Assistant works.
If so, you would either need the old server drive connected as an external disk, perhaps by using FireWire Target Disk Mode. It would not apply here, but if you for example had a Mac Pro originally running Snow Leopard Server you would be able to do a similar thing when migrating to a new Mac Pro running Lion Server by fitting the old hard disk internally and then be able to migrate from it.
In your case FireWire Target Disk mode sounds like the easiest option. See http://support.apple.com/kb/ht1661

Migration of Crystal Reports Server XI to new network server

We are running CR Server XI on an older network server that is becoming unstable. We would like to migrate CR Server and all its reports to a newer network server.
Given that there are around 200 reports published and being run from its current location, is there any way to easily move the program and reports? Any easy way to mass-change the ODBC database server info which is present in all these reports?

I wrote this a couple years ago and you may want to open a message with the deployment team to verify or get updated steps.
But this used to work fine when the version/patchwere the same in source/destination and was much faster then the import wizard.
you can migrate the CMS database from the CCM by selecting the copy from data source.
**CMS Source**
1) Prior to copying the CMS database it's easiest to simply disable auditing on the source CMS database to avoid errors on the destination.
**CMS Destination**
2) Create a CMS database or instance for the destination
3) Stop the CMS and all other services (page,cache,etc)
4) Double click on the CMS
5) Select the configuration tab
6) Choose copy from datasource
7) Click specify on the CMS Data source
8) Select source CMS database (make sure middle ware i.e. ODBC connection is installed)
9) Select destination CMS database
**CMS Source**
10) Stop CMS and all other services (page,cache,etc)
**CMS Destination**
11) Start the CMS
12) Login to CMC select servers, delete all servers associated with the source CMS if they exist
13) Stop CMS on the destination server
14) Double click CMS on the destination server
15) Select the configuration tab
16) Select the change CMS cluster name to (and choose your server or cluster)
17) Run regedit
18) Go to HKEYLocalMachine\Software\Businessobjects\suite 11.5\Enterprise\CMSClustermembers
19) Ensure that only the proper members are defined (i.e. your computer name only or your cluster members only). Remove anything that was added from the source system
**CMS Source**
20) Restart the CMS and all other services (page,cache,etc)
21) Login to CMC select servers, delete all servers associated with the destination CMS if they exist
22) Go to HKEYLocalMachine\Software\Businessobjects\suite 11.5\Enterprise\CMSClustermembers
23) Ensure that only the proper members are defined (i.e. your computer name only or your cluster members only). Remove anything that was added from the destination system
**CMS Destination**
24) Delete any directories in the businessobjects\businessobjects 115\filestore
25) Copy your FRS from the source businessobjects\businessobjects 115\filestore to businessobjects\businessobjects 115\filestore on the destination
26) Restart CMS - Done
NOTE: If XI replace 115 with 11. IF CE10 replace business objects with crystal enterprise and 115 with 10
Regards,
Tim

How to migrate SharePoint 2013 Content and Configuration DataBases to a new SQL Server and DataBases in it?

Hi,
We need to migrate Our current 1 clustered SQL Server, Many Configurations DataBases and Many Content DataBases to a brand new clustered SQL server and brand new databases in it.
How can I do this?
Can someone list the steps involved?
Thanks.

Hi,
According to your description, you want to move Content databases and Configuration databases to a new SQL Server, refer to this article:
https://technet.microsoft.com/en-us/library/cc512725.aspx?f=255&MSPPError=-2147217396
Besides, here is a similar post, you can use as a reference:
https://social.technet.microsoft.com/Forums/office/en-US/2cd46f7a-d583-41b2-82c2-ddc6d7c43fb8/how-to-move-sharepoint-databases-to-new-sql-server?forum=sharepointadminprevious
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Can you upgrade from 1.3.0.20 small ovf to 2.1 without migrating to a new server? It sounds like you can just adjust the server settings now.

Can you upgrade from 1.3.0.20 small ovf to 2.1 without migrating to a new server? It sounds like you can just adjust the server settings now. I am currently running 1.3.0.20 and I have enough to do with also needing to upgrade my wlc to 7.4.121.0 and getting the MSE up to 7.4.121.0 without having to stand up a new server if I don't have to. Please share any information you have in regards to your experience with coming from a version 1.2-1.3 small ovf and going to 2.1.
Thanks,
Andrew

You are better off standing up a new server. It's cleaner and safer..... you can always try to upgrade if you wish, but if things don't work out well, then you just wasted a lot of time. Snapshot the VM and export the floor plans, just in case. The ova is built around the DB size, so I don't know how well the DB will perform if you try to expand memory or drive space after an upgrade.
Please rate helpful post and Cisco Support Community will donate to Kiva
Scotty

How to migrate Sun One directory server to a new physical server install

need help
We have to move our existing installation of sun on directory server 5.2 to a new physical server.
We have a new physical server with a new host name. I am trying to find an easiest way to take a snapshot of our existing server and put it on a new installation
So will installing sun one directory server , its shows me two choices either to create a new instance or copy configuration from a existing server
What do i choose and which is the fastest route to replicate my old server
Thanks a bunch in advance
Sganb

Hi,
I'm glad you're still using the old, glorious Sun One Directory Server 5.2, because it brings me back a lot of memories... But are you seriously talking of the 'plain' version, with no patches/hot fixes on top? If that's the case, you're using of a software that has been developed in 2004 and released in Jan 2005! Just for you to be aware, in the last *8* (eight) years a considerable number (in the magnitude of 10^3) of bugs, security problems and performance issues has been identified and fixed...
However, to provide a better answer to your question, it would be important to understand the 'big picture' in terms of scenario and requirements:
1) Is this a critical 24x7 service for which you need to perform an on-line migration or you have a 'maintenance window' during which the service may be switched off?
2) Is the old server member of replication environment? If yes, how many masters/slaves do you have already? Shall the new server be part of this topology? What role shall it have?
3) Would it be possible to make the the old server able to communicate with the new server?
4) How big is the database that you've got to migrate? Do you have any requirement in terms of caches?
5) Do you take backups on a regularly basis and have in place working (*tested*) backup/restore procedures?
6) Is the new server conserving or changing the O.S. and architecture? [SPARC->SPARC, x86->x86, SPARC->x86, Solaris -> ? , 32 .vs. 64-bit? ]
7) What are the steps you did to 'install' the software on the new server?
Thanks,
Marco
P.S.: I don't wanna sound 'scaring' with all these questions, neither this should be intended as an 'hidden advertising' for Oracle Professional/Consulting Services, but the only way to not put in jeopardy your data is being aware of the risks, having the control of what's going on and ... possibly have a 'B' plan ;-)
P.S.S.: My last suggestion is to consider a migration to a later release AS SOON AS POSSIBLE; the latest is ODSEE 11.1.1.7, which is available here:
http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html
and seems to work pretty well ;-)

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

We currently have a 2003 R2 flat file server with multiple layers of nested network shares with over 2.5TB of data. We want to migrate to DFS on 2012 Server standard version with deduplication enabled. We have never worked with DFS and deduplication and
any white paper on DFS and deduplication would be greatly appreciated. Not finding anything on DFS step by step for 2012 and in particular migrating from 2003 file share to 2012 server DFS.

Thank you for the URL to your DFS write up. This was very helpful in my research of DFS. I have a couple of questions. Do I have to start DFS with two servers? I completely understand why you should have more than one server in the DFS pool (high
availability) but is it necessary? Also after setting up the two 2012 Servers with DFS, namespaces, and new shares managed by DFS manager, how do we migrate (move or copy) the existing shares to new server without losing the permissions? From what I've read
in your write-up all end users with have read and write permissions and admins have full. Also is there a best practice on how nested the shares should be setup within DFS? From looking at your write up the shares are one folder deep only. At this
company I'm migrating from a file server with shares 3-8 layers deep build up over the last 20 years.

Cannot migrate users print queues to new print server

I am needing to move the print queues on users computers to a new print server that I have set up by I am not able to do so. I have over 200 users at the office. I am thinking it is a problem getting to run it on the clients, but not sure where it is failing...
To start... I have moved the print queues from Server 2003 to Server 2008 R2. The machines are both 64 bit. I was able to export the drivers and the print queues to the new server using the print migrate tool. The names of the printers are the same on both...
The names of the print servers are different. I added a print queue to a test client and was able to print to it without a problem mapped to the new server, so that's not the problem.
What I can't do is use the script (see below) to remap the clients to the new server. I have tried and configured the script as a user log on script, configured a group policy and placed my test user in the OU. Rebooted the machine, logged
on with the test account but the print queues stay the same. I have even tried to run the script locally but still no joy... it runs but the queues stay the same. I used RSOP and see that the script is being applied... I am running Windows 7 Professional.
I really need to get this resolved as the server is being decommissioned within the month.
Option Explicit
Dim from_sv, to_sv, PrinterPath, PrinterName, DefaultPrinterName, DefaultPrinter
Dim DefaultPrinterServer, SetDefault, key
Dim spoint, Loop_Counter, scomma
Dim WshNet, WshShell
Dim WS_Printers
DefaultPrinterName = ""
spoint = 0
scomma = 0
SetDefault = 0
set WshShell = CreateObject("WScript.shell")
from_sv = "\\srvprint_1" 'This should be the name of the old server.
to_sv = "\\srvprint_2" 'This should be the name of your new server.
'Just incase their are no printers and therefor no defauld printer set
' this will prevent the script form erroring out.
On Error Resume Next
key = "HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Device"
DefaultPrinter = LCase(WshShell.RegRead (key))
If Err.Number <> 0 Then
    DefaultPrinterName = ""
else
'If the registry read was successful then parse out the printer name so we can
' compare it with each printer later and reset the correct default printer
' if one of them matches this one read from the registry.
spoint = instr(3,DefaultPrinter,"\")+1
DefaultPrinterServer = left(DefaultPrinter,spoint-2)
    if lcase(DefaultPrinterServer) = from_sv then
        DefaultPrinterName = mid(DefaultPrinter,spoint,len(DefaultPrinter)-spoint+1)
        scomma = instr(DefaultPrinterName,",")
        DefaultPrinterName = left(DefaultPrinterName,scomma -1)
    end if
end if
Set WshNet = CreateObject("WScript.Network")
Set WS_Printers = WshNet.EnumPrinterConnections
'You have to step by 2 because only the even numbers will be the print queue's
' server and share name. The odd numbers are the printer names.
For Loop_Counter = 0 To WS_Printers.Count - 1 Step 2
    'Remember the + 1 is to get the full path ie..
\\your_server\your_printer.
    PrinterPath = lcase(WS_Printers(Loop_Counter + 1))
    'We only want to work with the network printers that are mapped to the original
    ' server, so we check for "\\Your_server".
    if lcase(LEFT(PrinterPath,len(from_sv))) = from_sv then
        'Now we need to parse the PrinterPath to get rhe Printer Name.
        spoint = instr(3,PrinterPath,"\")+1
        PrinterName = mid(PrinterPath,spoint,len(PrinterPath)-spoint+1)
        'Now remove the old printer connection.
        WshNet.RemovePrinterConnection from_sv+"\"+PrinterName
        'and then create the new connection.
        'Do not create c6100
        if lcase(PrinterName) <> "c6100" then
            WshNet.AddWindowsPrinterConnection to_sv+"\"+PrinterName
            'If this printer matches the default printer that we got from the registry then
            ' set it to be the default printer.
            if DefaultPrinterName = PrinterName then
                WshNet.SetDefaultPrinter to_sv+"\"+PrinterName
            end if
        end if
    end if
Next
Set WS_Printers = Nothing
Set WshNet = Nothing
Set WshShell = Nothing

Hi,
àI added a print
queue to a test client and was able to print to it without a problem mapped to the new server, so that's not the problem.
àWhat I can't
do is use the script (see below) to remap the clients to the new server.
Based on your description, I understand that you have moved print queues to new print server via print migrate
tool successfully. However, when use this script (Remap Printer Connections) to re-map Printer Connections, the script seems to not be ran as expected. Meanwhile,
I noticed that you had ran the script locally. Did you find any error when ran this script?
On current situation, this issue seems to be more related to this Remap Printer Connections script. I suggest
that you would post it in
Official Scripting Guys Forum. I believe we will get a better assistance there.
If anything I misunderstand or any update, please don’t hesitate to let me know.
Best regards,
Justin Gu

Migrating from an OLD G4 Server to a new G5 Server

I have been running Server 10.5.8 on my G4 without a problem for the last year. Now we are upgrading to a new G5 server and was wondering how can I migrate the email accounts from my users.
I know that I have to export all my OD users and import them back in the new machine, setup the DNS (or can I copy these settings?) among other things.
This is our email server using IMAP and I just dont want to lose all my users emails. Is there an easy way of doing it?
TIA!

I did this from xServe G4 -> G5 Mac Pro -> xServe Intel a while back when our G4 died - while we don't run email on it, we do have OD Master, iCal, Wiki etc, and operate in "Simple" mode.
Each time I booted the "old" machine off the 10.5 DVD, and did a disk copy (image restore?) from disk to External drive, then did same on new machine and restored from External drive to server. The last time I did it (to Intel xServe) I had no authentication (corrupt LDAP I think) but an OD restore from a recent OD archive got that back up and running.
Considering it was 3 transitions from old to latest technology, I was pretty impressed it went so smooth...
Christiaan

Migrate licenses to new server no agreement #

I inherited a win2008r2 RDS licensing server that has win2003 cals & win2008 cals installed.
It used to be a citrix cal server as well, but the citrix util has been removed.
We replaced the citrix servers w/rds servers running win2008r2, however the new servers cannot connect to the licensing server…..the licensing server seems to be the problem so I am trying to replace it and migrate only the win2008 cals to the new licensing
server.
The problem is that no one who used to manage the licensing server has any clue how the win2008 cals were added to the original licensing server and thus they have no paperwork, agreement #, or anything.
How can I migrate just the win2008 cals to the new licensing server, given that I have no agreement #?
Thanks

Hi meetoo2,
How is the issue going now. Please let us know if there is anything that we could help.
Thanks.
Jeremy Wu
TechNet Community Support

Migrating from Essbase 7.1.6 to 9.1.3 that too to a new target server

Hi,
We have ASO cubes on Essbase 7.1.6. We are upgrading to Essbase 9.1.3 on a new target server. We want to migrate the ASO cubes (along with data). We know that we can get the data migrated by doing export and import. But this doesn't seem to be feasible as ASO cubes are big in number as well as size (as we want to move all the historical ASO cubes). Is there any other way to get the data from ASO cubes to new target server (and that too on upgraded Essbase 9.1.3)?

Since in version 7 you had to rebuild ASO cubes from source data, I suggest you do the same for your migration. Version 7 did not have an export function for your ASO cubes and MDX or report scripts for that version would be extremely slow for large ASO cubes.

Migrating to a new Messenger server

Similar Messages

Maybe you are looking for