Question on migrating production WLCs to a new WCS

I'm working for a client that has probably 8 or 9 sites, each with a
4402 WLC. They're now talking about implementing a WCS. Is there a way
to add these production WLCs easily, or do we need to wipe their
configurations and add them to the WCS server as if they were new?
Thanks!

You shouldnt have a problem but some things you want to keep in mind:
1) Make sure the WCS license is enough to cover all the access points for all 8 - 9 sites
2) Make sure the WLC can route to the the WCS server
You will not need to clear the configs of the WLCs. When you bring up WCS and add the controllers you can sync the controllers to WCS where WCS will learn the config of the controller...

Similar Messages

I migrated photoshop CS4 onto my new mac laptop. Error message on startup: Licensing for this product has stopped working. Error: 150:30

I migrated photoshop CS4 onto my new mac laptop. Error message on startup: Licensing for this product has stopped working. Error: 150:30 What do I do?

Uninstall and run the Cleaner Tool
Uninstall Creative Suite 4 and point products (Mac OS X)
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6

Question about migrating data from mac pro to new macbook

Hello all,
I ordered a new macbook today and i'm very excited. It will be the first time i've had two apple machines simultaneously. My question is in regards to getting my new macbook all stocked up with the files and apps currently residing on my mac pro.
1. I don't know if by using migration assistant if the data is removed from the old machine and added to the new. I don't want that. I want everything currently on my mac pro to remain, unchanged.
2. I'd normally use target disk mode, but no firewire on the macbook, so, no dice there.
3. My startup disk and apps and such reside on one HDD in my mac pro, while my home folder, or user files, or whatever, reside on a separate HDD. will this cause a problem.
Your input is much appreciated.

It can be done with USB, but it is slower and less reliable.
Ethernet works great, IF you have two FUNCTIONAL machines. The great thing about Firewire Target Disk mode was that if the HD/OS was corrupted, or the computer was for some reason unbootable you could still get data off of it quickly, without tools or special equipment. Firewire Target disk mode has saved my rear several times on every machine I have owned.
The hard drive is fairly easy to remove on the aluminum Macbook. I would remove it and install it in an external Firewire enclosure temporarily to transfer your files quickly and reliably, then put the drive back in the Macbook.
Firewire allows two operating modes. One is asynchronous, like USB which suffers from latency, bus contention and collisions.
The other is isochronous mode, and it lets a device carve out a certain dedicated amount of bandwidth that other devices can't touch. It gets a certain number of time slices each second all its own. The advantages for audio/video should be obvious: that stream of data can just keep on flowing, and as long as there isn't more bandwidth demand than the wire can handle, nothing will interfere with it. No collisions, no glitches.

Migrate product to another new product

Hi,
I have the following situation on NWDI CE 7.11:
- Product "xy" version 0.1 of "vendor.com"
-SC1 (version 0.1) developed with some dependencies to other SCs (e.g. WD SCs)
-SC2 (version 0.1) developed with some dependencies to other SCs
Now I want to create a new product as a new version of product "xy" and create an according track to start further developent on this new track.
- Product "abc" version 1.0 of "vendor.com"
-SC1 (version 1.0) developed with some dependencies
-SC2 (version 1.0) developed with some dependencies
Hope can I do this? Are there any tutorials? I think the problem is to change the product name and version at the same time and migrate the developed SCs with new version numbers...
Thanks ahead,
Bernd

So you mean I have to define a new product first. After that I should create new SCs in the SLD and assign them to the product. There is no copy mechanism where I can change version numbers and names?
When I create the new SCs there are different options:
- Create new version for an existing SC
- Copy my SC with dependencies to a new Version
Where is the difference?
After that I could create a new development track and add new newly created SCs? The other required SCs are added automaticaly?
Thanks ahead!
Bernd

HT1338 Migration assistant problems setting up new Macbook pro.... System preferences will not open and Mozilla products do not open "profile missing"???

Used migration assistant to set up new Macbook pro from old macbook pro. Many "profile" problems.
Will not even open "System Preferences" for user whose profile info was transferred. (Will for "Administrator")
Cannot use Firefox or Thunderbird, profile missing.
Help???

Launch the Console application by entering the first few letters of its name into a Spotlight search, and look under "User Diagnostic Reports" for crash logs related to the application(s). Select the most recent one and post the contents -- the text, please, not a screenshot. For privacy’s sake, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report.

WLC 4406 Migration to WLC 5508

I have to make a migration from a controller to oher.We have now in production a WLC 4406 with 90 AP in local mode and HREAP mode, and we have to change the WLC to other new model 5508.
Do somebody know which one could be the best method to do that???
Thanks for your HELP and Time....

Ths is true Salil, but very few companies are running the VPN module in the 4400. thankfully it was EOL'd shortly afte Cisco bought Airespace.
and the upload check that runs, will alert you to any config that is wrong.
HTH,
Steve
Please remember to rate helpful posts or to mark the question as answered so that it can be found later.

Need to transfer/migrate production server from HP-Unix to SuseLinux 11.5

Background : We are having ECC 6.0 running on HP Unix
What we need to do : want to migrate the entire production application to a new server under o/s SuseLinux 11.5 certified by SAP AG
What we are doing : there is a utility called Software Developer Tool DRYRUN using this utility want to export application to storage and from store we shall restore the application into the new server under o/s SuseLinux 11.5
What error I am getting :
Sapinst could not find the required software logistics java libraries DIAGNOSTS. The global directory may not be available at u2018/usr/sap/fpp/flobalu2019 or its contain may not be up-to-date in addition the version of the SAP NetwWeaver java system might be lower than AP6. SOLUTION, Mound the global directory and/or apply the latest support package.
Using above method we could migrate development server to SuseLinux 11.5 successfully.
If I have posted this question on wrong forum pl. guide me
Thanks
Nitin

Hi Nitin,
Just to check with you, OS/DB migrations has to be performed following certain rules. HPUX is big endiand and Linux is little endian so an Heterogeneous system copy should be performed and theres only a few supported ways to perform the migration. Have you check that the usage of DRYRUN is ok and that your system will be supported after the migration?...
Regards
Juan

Migration from old Mac to new mac 27 inch

Just a quick question on migration of data & applications.
I have 10.5.8 on my old Mac & have ordered a new 27 inch Imac which will be delivered next week.
Reading the migration process I have one query.
My new Mac will have OSX 10.6 - the new ilife 2011 programs - so my question is whilst I want my old photos, movies, data and applications that will not be on the new computers do I transfer (migrate) across in migration the old iphoto & Ilife 2010 applications and operating systems
thanks

+Last question I promise.+
It has really not so much to do with "getting the best" out of it; rather, it has to be formatted correctly to work (i.e. most hard drives come formatted for Windows). So, depending on which brand you get, it's best to format it just to make sure. Note: you do not really need any included software, the Mac built-in Disk Utility does a fine job. Once you power it up and plug it in, you'll get an icon on your desktop. Now open Disk Utility, find that hard drive on the left, and choose the "partition" tab. Once there, make sure to choose "Mac OS Extended (Journaled) and, under options, choose GUID partition table. You can then also name it and/or partition it if you want (don't forget to name each partition, i.e. HD backup, photos, whatever). Click on apply. You'll get a warning that everything on it will be deleted - that is ok. Once done, you'll have the newly named partition(s) on your desktop and are ready to go.
Another note: if you're planning on using Time Machine, read all the tips (Pondini's) in the TM forum. I don't use it, so I can't help there (I create bootable clones on mine instead).
Final note: when you reply on these forums, it makes it easier if you click on the reply button of the person you are responding to - otherwise we don't know which one of us should respond to your last question....

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

Question re: Migration Assistant

Brief question regarding Migration Assistant:
We currently have an iMac in the office that's about 3-4 years old (specs associated with this iMac are posted along with this question, of course). We are going to be acquiring one of the brand-new 27 inch iMacs at the end of this month.
The old iMac only has USB 2.0, along with FireWire 800. The new iMac only sports USB 3.0 and Thunderbolt.
Therefore, in order to use Migration Assistant I'm assuming I will need to get adapter cables…? What exact adapter cables are recommended under the circumstances?

I'm assuming that the Thunderbolt to FW800 adapter sold by Apple would work on the new iMac (I didn't even realize that there was no FW support on them - I'm not in the market for one - but I think that the handwriting is on the proverbial wall when it comes to FW).
I would call Apple or drop by your local Apple Store just to confirm that the TB>FW800 adapter will work on the new iMacs.
I'm sure glad I'm cutting my FW drives loose and going with TB drives now...
Clinton

Questions about migrating Exchange 2010 to 2013

We currently have two Exchange 2010 servers with roles separated. One local mailbox server without CAS in our building and a CAS with no mailboxes in a remote datacenter.
We plan to migrate to 2013 with two new servers hosting all roles on each and then shut down the 2010 servers. There will be one local and one in a datacenter for Exchange 2013 so that either server could be individually restarted without internal LAN users
losing email access. (We do not want to open network access from the Internet to the onsite CAS). Is it practical to set it up this way?
How do we get the existing certificates (mail, autodiscover, and the local host name etc.) moved from the 2010 to the 2013 to the new servers when I assume they both must be running side by side for at least a short time while mailboxes are moved form 2010
to 2013? Will we need to buy new SSL certificates since the local host machine names for the Exchange server 2013 servers will be new and there will be more than one CAS?

Most of the CAs allow issuing duplicate certificate (as if you are requesting for a new cert) for the servers running same application. If your CA doesn't provide duplicates you can export the certificate and import to Exchange2013. http://msexchangeguru.com/2013/06/29/import-cert-e2013/
In certificate you dont need your internal FQDN. Especially in future you wont be able to add your internal FQDN in your certificate as most of the CAs wont allow you to add internal FQDN.
When you migrate to exchange 2013 you just need to configure the external URLs of Ex2010 in Ex2013 for both (i.e. same URLs for internal and external URLs) and point your common name and autodiscover to Exc2013 as Ex2013 will proxy the requests to your legacy
Ex2010 server. i.e. Your client interface will be Ex2013.
Please check this it will help you configure Split DNS and configure your URLs
http://exchange.sembee.info/2013/install/clientaccesshostnames.asp
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/ GUI
Configure split DNS to resolve external name from internal network.
Keep both Ex2010 CAS and Ex2013 CAS servers till all get logged in atleast once to connect to Ex2013 mailbox automatically.
As your DAG stretched across the data centers make sure
your DAG is in DAC mode.
http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
Please read this as well for details about DAG configured in multiple site
http://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
Ensure you use Exchange2013 SP1 as it is already released and available for download
http://www.microsoft.com/en-us/download/details.aspx?id=41994
Do you have a load balancer in place?
Regarding internet facing it depends. You can configure CAS2013 server in DMZ if you wish to.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

How to Migrate the 12 Hives to new server in new farm

Dear All,
How could I migrate the 12 hives to new folder ??
Are there specific folder I just copy/past or I just copy everything and override the original ?
Thank you

My first question would be why? Any customizations, hopefully, should be in .wsp format.
Assuming you have manually copied files into the hive folder and are looking to get them to the new server, copying the whole hive across is a really bad idea. What I have done in this situation (more than once) is to use a differencing app such as Notepad++
(with plugins) or WinMerge (my personal fave).
1) Copy the hive from the source server to a temp folder on the destination server
2) Use one of the apps above to compare the two directory structures
3) Copy across just the missing files from the source folder to the destination hive
By doing it this way you ensure you don't damage your fresh clean hive on the new server, and you should be able to get across the manual customizations you need.
Good luck!
-Corey

After upgrading to NX-OS 5.04, out snmp traps monitoring system is not generating ticket / incident for the snmp traps and my question is whether we need to apply new MIBS for that?

after upgrading to NX-OS 5.04, out snmp traps monitoring system is not generating ticket / incident for the snmp traps and my question is whether we need to apply new MIBS for that?

Looking at the error message "The Network Adapter could not establish the connection" , It appears hostname and port may be incorrect. Review the targets.xml under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\emd and
emoms.properties under E:\oracle\product\10.2.0\db_1\SAP_solman_SDB\config folder to make sure host ( sap_solman) and port (1527) are correct.
As far as setting the environment variables goes, you can go to control panel -> system -> advanced -> environment variables and set the ORACLE_HOME and ORACLE_SID
-Ramesh

Can I migrate multiple reports to a newer version at the same time?

If I have an older version of Crystal Reports can I migrate them all to a newer version at the same time? Is there some documentation that will provide instructions? I dont' want to have to upgrade them one at a time.
Thanks - Mike

There is no utility that will do that for you. Not from SAP. Perhaps some 3rd party (google Ken Hamady), etc. Or, you could create an application in VS .NET or java to do it though.
But depending on what you are migrating from and what you are migrating to, you may not need to do any updating at all...
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

Migrating from old MBP to new

I've just purchased a new MBP 17" i7 to replace my 2008 MBP 15". When I got my 2008 version, I just used the Firewire 800 to move all of my stuff from my iMac to my MBP. Spent a few minutes fixing some passwords, and that was that. Probably took around an hour.
So, I haven't migrated between Macs for a couple of years, and I want to find out what the best way to proceed. I use Time Machine to back up my computer, and have all of my iTunes media files on a portable 1TB hard drive (I've got thousands of songs in Apple Lossless). So here are my questions:
1. Should I migrate from my old to new via Firewire? Or is it best to restore from Time Machine?
2. Will Time Machine "start over." Will I lose 2 years of incremental backups? It's nice to know I can go digging back a couple of years to find that file I shouldn't have erased. Also, every once in a while a piece of music gets corrupted, and I've got to get it replaced by an older saved version.
3. This might not be the right place, but will I be able to point iTunes on the new MBP to my media files? I'm convinced I can, but I'm not sure.
I'm going to wait a few days to do the migration, because I want to do this right. A few years ago, I did it wrong and lost years of photos, of which 90% were lost forever.

OrangeMarlin wrote:
So, I haven't migrated between Macs for a couple of years, and I want to find out what the best way to proceed.
+Setup Assistant+ has been greatly improved for Snow Leopard. See #19 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).
1. Should I migrate from my old to new via Firewire? Or is it best to restore from Time Machine?
Makes little difference. It's a bit easier from Time Machine, since you don't have to start up the old Mac in Target Disk mode and make the connection, but otherwise it makes no difference (assuming you didn't exclude anything important from Time Machine).
2. Will Time Machine "start over."
As William says, yes.
Will I lose 2 years of incremental backups?
Depends on how much space is on your Time Machine drive.
It's nice to know I can go digging back a couple of years to find that file I shouldn't have erased. Also, every once in a while a piece of music gets corrupted, and I've got to get it replaced by an older saved version.
Yup, absolutely. If you keep the old drive "on the shelf" you can always display and restore from it via the +*Browse ...+ option, per #17 in the FAQ.
Or, if you get a new, larger drive, you can copy the existing backups to it, and continue backing-up to the same set of backups. See #18 in the FAQ. If you do that, when the first backup of the new Mac starts, you'll get the prompt in #B5 of Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).
3. This might not be the right place, but will I be able to point iTunes on the new MBP to my media files? I'm convinced I can, but I'm not sure.
Yup. Just hold down the Option key while starting iTunes; you get a prompt to Create a library or Choose an existing one.
I'm going to wait a few days to do the migration, because I want to do this right. A few years ago, I did it wrong and lost years of photos, of which 90% were lost forever.
I'd recommend against that. +Setup Assistant+ runs immediately when you first boot the new Mac up; if you take all the defaults, it will move everything from the old Mac (or backups) except OSX. No temporary user profile, no setting-up communications, etc.
If you're nervous about losing things, and don't have secondary backups, do your final Time Machine backup of the old Mac, and turn it off. Use the backups to transfer your data, so the old Mac won't be involved at all.

Question on migrating production WLCs to a new WCS

Similar Messages

Maybe you are looking for