Question on Migration

Hi All,
We are planning to migrate Business objects 5.0 to XI 3.1 SP2.
Could you please be knid enough to let us know what precautions and suggestions we require to accomplish this..
Basically, we would like to know how its going to affect the security rights? or should we again modify the rights in XI 3.1.
Also any suggestions on database/tables front?
Please suggest.
Thanks,
Kavitha.

1. you need to be at 5.1.4 or even 5.1.9 version of 5.x to be able to migrate.
2. You should re-design security model in Xi3.1 and not try to use the same as one in 5.x
3. Report formatting and some calculation engine changes will affect how your reports run in Xi3.1 vs 5.x, so you should deploy Xi3.1 in a test environment, migrate most common reports and test them to see how they run and what happens.
4. Xi3.1 is a completely new architecture. Review Admin, Deploy , Install and Migration guides from http://help.sap.com/businessobjects prior to attempting any migrations.

Similar Messages

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

SAP Adapter Best Practice Question for Migration of Channels

I have a best practice question on the SAP adapter when migrating an OSB project from one environment (DEV) to another (QA).
If my project includes an adapter channel that (e.g., Inbound SAP Proxy listening on a channel), how do I migrate that project to another environment if the channel in the target environment is different.
I tried using the search and replace mechanism in the sbconsole, but it doesn't find the channel name in the jca and wsdl files.
What is the recommended way to migrate from one environment to the other when the channel name changes?

I have a best practice question on the SAP adapter when migrating an OSB project from one environment (DEV) to another (QA).
If my project includes an adapter channel that (e.g., Inbound SAP Proxy listening on a channel), how do I migrate that project to another environment if the channel in the target environment is different.
I tried using the search and replace mechanism in the sbconsole, but it doesn't find the channel name in the jca and wsdl files.
What is the recommended way to migrate from one environment to the other when the channel name changes?

Quick question re: migration of nat exemption from asa pre-8.2 to post-8.2

I am going through http://www.cisco.com/en/US/docs/security/asa/asa83/upgrading/migrating.pdf and I have a question about nat exemption. According to the guide above, the migration of nat exemption will look like this:
access-list inside_nat0_outbound extended permit ip vLan201 255.255.255.0 172.19.252.0 255.255.255.0
nat (inside) 0 access-list inside_nat0_outbound
object network obj-vLan201
subnet vLan201 255.255.255.0
object network obj-172.19.252.0
subnet 172.19.252.0 255.255.255.0
nat (inside,any) source static obj-vLan201 obj-vLan201 dest static obj-172.19.252.0 obj-172.19.252.0
My question is this: if acl inside_nat0_outbound has multiple ACEs, does the migrated configuration contain a separate "nat (inside,any)" statement for each ACE in the original pre-8.3 config, like this?
access-list inside_nat0_outbound extended permit ip vLan201 255.255.255.0 172.19.252.0 255.255.255.0
access-list inside_nat0_outbound extended permit ip vLan201 255.255.255.0 172.19.253.0 255.255.255.0
nat (inside) 0 access-list inside_nat0_outbound
object network obj-vLan201
subnet vLan201 255.255.255.0
object network obj-172.19.252.0
subnet 172.19.252.0 255.255.255.0
object network obj-172.19.253.0
subnet 172.19.253.0 255.255.255.0
nat (inside,any) source static obj-vLan201 obj-vLan201 dest static obj-172.19.252.0 obj-172.19.252.0
nat (inside,any) source static obj-vLan201 obj-vLan201 dest static obj-172.19.253.0 obj-172.19.253.0
Our current acl has about twenty entries, which would make for twenty nat statements, if this is right.
Thanks,
-Mathew

Hi,
Default behaviour for NAT past 8.2 software level is to let traffic flow through the ASA without NAT. Before that "nat-control" setting on the ASA defined if the traffic needed a NAT configuration or not.
If your NAT0 / NAT Exempt configurations contain statements meant for VPN connections then you have to make new ones for those.
Are the entries in your old NAT0 configurations meant for traffic between different networks in your own LAN or are they meant for different VPN connections? Or perhaps both.
But as you said, moving to the new software does mean that even some simple NAT configuration will now contain more configurations than in the old software.
- Jouni

Two questions before migrating to Revel

Hello,
Two questions, please:
1. I chose Photoshop.com because it was the only service which did not reduce the photo quality of the files I uploaded. Will Revel maintain that same policy?
2. If I move the photos, will I need to update any link of any file I shared through Photoshop embed api? (the api.photoshop.com... links I got from the "share button") or you will redirect those links to a new address on Ravel? Will Ravel allow me to embed my pics at all?
Thanks.

1) Revel will retain the resolution of the files when you move them.
2) If you allow the files to be migrated, then any links previously used from photoshop.com will be redirected to Revel and should still work. If you archive the files back to your computer and then add them to Revel manually (not using the migration offer), or if you add new files then you will need to send new links to Revel.
Pattie

Questions upon migrating to MAC

Hello All,
It's my pleasure for me to join this community.
I am looking for a replacement for my Windows XP pc.
While on it me seriously considers the MacBook pro as one option.
However several generic/high level and several specific questions arise
regarding the switch from win to mac.
Where will be the best place to ask all such questions?
Best Regards

Thanks a lot for all your answers.
I will need a replacement for my current Windows pc.
The new solution should provide me also with more mobility.
The main application/usage will still be mainly desktop,
though I wish to have with the new solution more mobility than it is
the case with current one.
That is the reason of my statement I consider switching to MacBook Pro (+Ratina).
So, you are right. It will be migration in two ways:
pc to mac
stationary to mobile
I think local retailer is one of the worst solutions, for two reasons:
- it can provide me with opinion of very limited circle of persons
- have had bad expierence with such just last weekend, unfriendly, unopen to listen to my needs

Question on migrating the entire app directory.

Hello all, We are upgrading Essbase from 11.1.1.4 to 11.1.2.3. As a part of the migration as you all know one is supposed to copy the app directory over to the new server(target server). My question is does the source server have to be down when this app directory is getting copied over to the target server?On our dev server the copy took 12 hrs. So we are looking at ways to reduce the downtime on production. The essbase staging tool shuts off the source essbase server as a part of the migration and then one of the succeeding steps is to copy over the app directory. Now once the copy has been started can the essbase server be started(to reduce down time) while the copy is in progress or is it a must that the source must be down. Thanks for your suggestions.
Thanks,
Ted.

Thanks for the suggestion John, I will take the two step approach. Just one more question though, So When you say "hit on performance while copying the files" does it imply that the source can be up and running when copying locally? Thanks again.
Ok, just understood what you were saying, copy the app directly locally( after shutting of essbase on source) . Once the local copy is complete, bring the application back up, and then copy the local copy to target( and it is during this copy that there could be an impact on performance).
Thanks,
Ted.
Message was edited by: Teddd

Question on Migration Assistant

My new Macbook Pro (13 inch) is arriving in few days. Currently i have a Macbook (Matte Black) which i have been using for 2 years.
I wish to migrate all my stuffs to the new Macbook Pro. Once this is done, what happens to all the application and other stuffs on the Old Macbook. Will it be empty like when it was new?
I want to give my old macbook to my lil brother. I am worried on Microsoft Office application such as Word, Power point, excel etc. Will all these be gone?

Ok guys i understand what you all mean. But what i am trying to do here is using the microsoft office in 2 different macs.
My friend and me bought microsoft office and it came with 3 numeric keys. 3 of us shared the keys and installed in all the 3 macs. Mine was installed in the macbook (black).
Now i am trying to migrate those to the new macbook pro. Obviously i can use that on the new macbook pro. My question is will it be still usable in the old macbook? I find it weird if its stil usable in the old mac. Coz if that was the case, i can distribute that microsoft office to other users as well. No point having the 3 keys.

How can i directly put up my question to migration work bench

i mean...
if i have a question and nobody answers it then is there any other link on which i can post the same mesage and the site owner answers it....
null

Appologies for the error.
Our support email is [email protected]
other details which may be of use:
a web site with an FAQ and a Quick Tour: http://technet.oracle.com/tech/migration/workbench/listing.htm
an Oracle internal web site: http://mtg.ie.oracle.com/mtg/
Turloch
Oracle Migration Workbench Team
null

New iMac Question - Rosetta & Migration Assistant

I'm getting a new 27-inch iMac in the next few days but I have a couple of questions beforehand. I still need to use some Rosetta-based apps so will I have to install Rosetta on the new 27-inch iMac or is it already pre-installed? Seems to me that I've read somewhere that Rosetta is a "custom-install" with Snow Leopard.
This leads me to the next question about the Migration Assistant. I will need to transfer my data from the old hard drive to the new 27-inch iMac. The easiest way being with the Migration Assistant. In the past, when I've bought a new Mac and right after connecting the new Mac and my old Mac together via FireWire and starting the new Mac up for the first time, I've just transferred the data right away before even setting up a new user account on the new Mac. But if I do this now and Rosetta isn't yet installed, will my old apps and related files be transferred properly?
I guess what I'm getting at is this - should I boot the new 27-inch iMac up first, then install Rosetta (if an install is needed), then set up a user account on the new 27-inch iMac and then run the Migration Assistant to transfer data from the old hard drive? Or should I just run the Migration Assistant on the very first startup of the new 27-inch iMac and transfer the data right away?
I hope this makes sense. Thanks for any help you can offer. I'm trying to plan this out properly in advance and I don't want to mess anything up.
Gerard

I know this was long ago - a day or 2 after July 3, 2009 (purchase date of our iMac) - but here is what happened:
Connected old computer (eMac) to new iMac to start "Migration" software. Waiting for boot and recognition extremely long.
Choices came up to migrate EITHER software or files.
I swear I selected "files" but it migrated software, over an enormous time.
Takes too long to migrate, so when I discovered no files were transferred, I went to old computer to copy data to DVD and "migrate" manually.
Went through that process on eMac; DVD burned; eject DVD and take to iMac.
I "trashed" the folders from the eMac (they were not needed on the old computer).
Guess what? The DVD DID NOT burn all the folders that I told it to burn.
Data lost: Several years of tax information! Teaching files! I don't even know what else!
Best of all, after talking to a certified Apple technician who happens to be a friend, he doesn't think there is any way to recover that data.
Why in the **** would I migrate applications (is that legal?) to a new computer?! That software's FIRST focus should be to preserve DATA, also known as FILES.
I know that I made some errors in this - - ERRORS IN CONFIDENCE IN APPLE!
Can you help? Can you send me software to recover my files? Can I have it today or tomorrow? That's when I need the info for my tax filing and FAFSA applications for 2 (TWO!) children to go to college next year.

Several questions about migrating from iPhoto to Aperture

I'm currently a heavy iPhoto user and am looking into migrating to Aperture. Can anyone give me a sense of what I to expect if/when I make this switch?
Here are several particular things I'm wondering about:
1. iPhoto works great as a computerized photo album for casual browsing. (I can see a page of different events with mouse-over previews, plus I can hide poorer shots so that I can just view the highlights.) Will Aperture be a step back in this department? If so, is it possible to "share" my Aperture photos with iPhoto without keeping two parallel copies of everything?
2. When I import an edited photo from iPhoto to Aperture, will the iPhoto "original" become the Aperture "original" and the iPhoto "modified" become the Aperture "modified? Is the same true if I export an edited photo from Aperture to iPhoto?
3. Does Aperture have an analog for "hidden" photos? I currently mark my best shot from a series by hiding the rest. Will I lose this marking if I migrate to Aperture or is there a way to preserve it?
4. I currently have a number of short video clips (taken with my point-and-shoot's video feature) mixed in with the iPhoto albums. (iPhoto really does let me keep everything organized in one place!) If I understand correctly, Aperture won't let me store these in my Aperture library alongside the still-photos of the same subjects. Is this correct? If so, how have other people handled this?
5. Do EXIF tags get re-read upon import from iPhoto to Aperture? I've got a number of iPhoto files which I've retroactively geotagged with HoudahGeo. Will the tagging be lost (since iPhoto is not currently aware of the geotagging as the EXIF tags have not been re-read)... or will Aperture now recognize this metadata?
6. If worst-comes-to-worst and I give up on Aperture after a few months, how painful will it be to un-migrate back to iPhoto? More importantly, what album metada (e.g. events, albums, ratings, tags, notes, dates, hidden-ness, links between original and modified versions of a photo, iWeb references, etc.) will be lost? In other words, if I were to import everything from iPhoto to Aperture, wipe my iPhoto library clean, and then export everything back from Aperture to iPhoto, what information will have been destroyed?
Thanks in advance for any answers to this long list of questions!

Here are several observations (read: warnings) in case anyone else is considering migrating a significant iPhoto library to Aperture...
A) Pictures marked as "hidden" appear to be silently skipped over (along with video clips, as was expected) when importing an iPhoto library to Aperture. They do not appear in the relevant Aperture project regardless of the filtering options.
B) Both iPhoto originals and modifieds are imported. The former are given the keyword "iPhoto original" and the latter are given the keyword "iPhoto modified." Each pair of photos is put into a single Aperture "stack." Both photos are given the same tags/ratings (so, for example, the un-rotated, uncropped, poorly balanced original will show up alongside the nice clean "modified" if you were to filter for 5-star images), and both files are given identical "version names" (equal to the "name field" in iPhoto). In most cases the original -- not the modified version -- was set as the stack's "pick" and displayed when the stack was collapsed. *Significantly, I could find no way of creating a view in Aperture that showed one copy of each picture, with the "iphoto modified" version displayed for photos that had been modified in iPhoto and the original version displayed for photos that had never been modified in iPhoto!* (This is, of course, the way they are shown in iPhoto.)
C) My understanding of "stacks" is that they are designed to help organize multiple "tries" at the same shot (e.g., I want to make sure that nobody's eyes are closed in the group photo, so I press the shutter six times in quick succession -- I'm going to pick a "best" one will be mostly interested in that shot from then on). This is a fantastic idea! However things get confusing if you are already using stacks to track original and modified versions (as described above)... particularly if your stack should contain six pictures plus original versions of each. Plus, as I mentioned, the "original" version is usually the default "pick" in each stack.
D) After import, "iPhoto original" versions of portrait photos appear un-rotated. Normally, my cameras (including a Nikon D80, an iPhone, and others) mark photos' orientations and they are automatically displayed in the correct orientation. Aperture appears to consider this auto-rotation an iPhoto edit and helpfully displays the "iPhoto original" always in landscape.
E) Aperture may incorrectly import events whose names contain a "/" or a ".", so if your event names contain dates, rewrite them with "-"s before importing to Aperture.
F) Aperture does have a rough mouse-over-the-icon-to-flip-through view, similar to the "events" pane in iPhoto... although you will lose your choice of which photo serves as the default icon for each event when you import your library from iPhoto, and you cannot "hide" photos from appearing in the flip-through as you can with iPhoto.
G) Perhaps it's my inexperience with the program, but I could find no way to sort the project list by date (vs. alphabetically), nor could I find any way to make a correction to a single photo's date/time.
As a bottom line, remember that Aperture is definitely not "iPhoto Plus." It lacks a number of iPhoto's features, but in exchange gives you a number of really slick tools aimed at streamlining a digital photography workflow.
I'd also encourage people to think very carefully before moving a large, well-organized iPhoto library to Aperture. You may lose a fair amount of information, and the result will take a lot of work to "make pretty" again. It does look like a nice program, though. Are you ready to relegate all of your existing pictures to an iPhoto "pre-history" and start over with a blank -- but much fancier -- slate in Aperture?

Questions about Migration Assistant

I'm getting ready to move the contents of my G4 iBook to a new Intel-powered MacBook. I assume Apple's Migration Assistant can handle a lion's share of that job but I have a question...can I change the UserName (and ShortName) on the new computer and still migrate everything over with the Apple utility? For example, a particular concern is how to handle the information contained in Keychain. When that file gets moved over, how do I make it the default Keychain and set it to unlock with the new computer's password?
And any other issues I should be aware of when moving from a G4 machine?

Actually you cannot migrate a user folder that has the same name as one already created. However, because you are moving from a PPC to an Intel Mac there are some cautions of which you need be aware:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3 or G4 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior (does not work), TechTool Pro (pre-4.5.1 versions do not work), SuperDuper (newest release works), and Drive Genius (untested) may not work properly on Intel-Macs. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode or copying the critical contents to CD and DVD or an external hard drive will work better when moving from PowerPC to Intel Macs.
Basically the instructions you should follow are:
1. Backup your data first. This is vitally important in case you make a mistake or there's some other problem.
2. Connect a Firewire cable between your old Mac and your new Intel Mac.
3. Startup your old Mac in Target Disk Mode.
4. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
4. Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/com.apple.mail.plist (* This is a very important file which contains all email account settings and general mail preferences.)
/Home/Library/Preferences/ copy any preferences needed for third-party applications
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
Credit goes to another forum user for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.
Be careful about what you migrate. Migrating an entire user folder is not a good idea when moving from PPC to Intel. Stick to your movable folders as described above.
PPC applications may not work after migration. If they don't then simply reinstall them.

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.

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.

WiSM questions (requirements, migration and some config)

Hello,
I am going to be installing a CISCO WiSM blade in a 6509 switch to replace my dual 4404's and I am having trouble finding answers to some of my concerns.
On the documentation I could find, one of the requirements listed to run WiSM is ACS version 2.6. This isn't too big of a deal as I have ACS version 3.3 running, but my question is this:
Is ACS a requirement to actually use the WiSM - or is it just saying that if you are using ACS with the WiSM, you need 2.6 or above? I do not use ACS with my 4404's.
More importantly, I have a question regarding the actual migration process of switching from the dual 4404 setup to the WiSM blade. I do not have a second 6509 for testing/configuring purposes, so the only way to set up the WiSM is live.. so I'd rather not have to configure it from scratch. Is it possible to upload configuration files from each 4404 into the two internal 4404's of the WiSM blade? If so, how?
Thanks in advance.

You do not need ACS to use the WiSM. Its just saying you need that version level if you plan on using ACS with the WiSM.
For testing I suggest you make a new vlan/dhcp scope that you can run only on the wism. For this dhcp scope set the option 43 value to point only to the WiSM. This way you have it live, but not on the production wireless network.
Once you have finished your testing and feel comfortable with getting things configured you can wipe out the interfaces/ssid's on the wism for your test network and put in the production settings.
I have 5 wism's installed currently with over 1000 AP's, 2 location servers, and WCS. So if you need any help getting things running let me know.

Questions about migrating to a Mac Pro from an old MacBook Pro

My present setup is a 2006 MacBook Pro with 3 external drives. One external eSATA RAID1 for music, another eSATA RAID1 for photos and video/movies, and the 3rd (FireWire) is for Time Machine. The internal 320 GB boot drive has 2 Boot Camp partitions for Windows XP SP3 and Windows 7.
Here's the new setup (as purchased):
• Mid-2010 ( MacPro5,1 ) Mac Pro 6-core 3.33 GHz
• 8 GB RAM (4x2 GB)
• 8 TB HD (4x2 GB Seagates)
• Apple RAID card
Mulling this migration over, these are the things I'm wondering about:
• I'll probably keep the 4x2 GB internals as a group, either going with two 2x2TB RAID1 volumes or perhaps considering a single 4x2TB RAID10 arrangement. The latter makes me a little nervous‡.
(‡ +Why? Not a fan of striping in general - plus, with my present setup, a problem with one of my Venus eSATA RAID enclosures was easily testable by removing the disks from the other "good" enclosure and substituting the other "bad" enclosure's disks to test inside a "good" enclosure - i.e. it was nice to have redundancy+ ).
Q. *Any thoughts either way on going with 2xRAID1 vs. 1xRAID10?*
Q. *Any Apple RAID card horror stories?*
• Therefore, I'm thinking of adding a cradle and disk(s) to the ODD_SATA ports. Probably a 256 GB SSD at a minimum for the boot drive.
Q. *Any issues booting OS X from an ODD_SATA-connected SSD?*
Q. *I understand you can't use Boot Camp on Apple RAID card-connected drives. True?*
Q. *I also seem to be reading that you can't boot Windows in any guise from an ODD_SATA-connected drive (SSD or HDD). True as well?*
Am I screwed? Forced to keep the MacBook Pro around for Boot Camp, no way to run it on the Mac Pro with this configuration?
• Memory. I understand these boxes run their memory with Triple Channel.
Q. *It sounds like at the very least I should rip out the 4th 2 GB DIMM. Probably replace all 4 with 3x4 GB or 3x8 GB (ECC) DIMMs, right?*
Yikes. Long post. Sorry. That's enough for now, I think.

now-disconnected iPass port
I don't think the 2010 model you ordered HAS an iPass port. The new Apple RAID card does not use one.
Follow a complicated procedure for trying to get the Mac to run all the SATA ports as AHCI so that Windows would 'see' all 6 of the SATA ports instead of what I presumed to be the current situation,
I don't think that applies to 2009 and later models either. The six SATA port are all listed in my Mac PRO as AHCI and all should be equivalent:
Serial-ATA Device Tree
-Intel ICH10 AHCI
. HL-DT-ST DVD-RW GH41N
-Intel ICH10 AHCI
. HL-DT-ST DVD-RW GH41N
-Intel ICH10 AHCI
. WDC WD360GD-00FLA2
-Intel ICH10 AHCI
. Kinston SSDNOW 30GB
Intel ICH10 AHCI
Intel ICH10 AHCI
You sure are digging up some stale information in your research
... but you are rapidly becoming an expert on the way it USED to be.
Now take the essence of what you posted just above, start a new topic, give it a catchy title, and see what other Users have to say!
Message was edited by: Grant Bennet-Alder

Question on Migration

Similar Messages

Maybe you are looking for