Migrating Exchagne Server 2007 to 2010 DAG....

Hi,
One of my customer request to migrate their existing Exchange server 2007 to a latest version. They are currently using Office 2003 package so I think we can only migrate to Exchange server 2010 due to compatibility issue of Office Outlook with Exchange 2013.
We need to implement DAG solution with 2 server and I know that I can install Exchange Server 2010 SP3 over Windows Server 2012 stranded edition. We hope to implement one server in the Head office and the other server is gong to be fixed in DR site that
connects the Head Office via a IPSec VPN tunnel.
We have several ADs. 3 in Head Office, One in remote site and one in DR site.
HO-Primary AD   :   Windows server 2003 R2 32bit    Standard    :   Schema,Domain,RID,PDC,Infra and a GC
HO-DC01       :   Windows server 2008 R2 64bit Standard    :   GC
HO-ADC       :   Windows server 2008 R2 64bit Standard    :   GC
ROADC       :   Windows server 2008 R2 64bit Standard    :   DC
DR-ADC       :   Windows server 2008 R2 64bit Standard    :   DC. Will change to GC when installing DAG
Domain Functional Level   :   Windows server 2003
Forest Functional Level   :   Windows server 2003
Current Exchange 2007 setup has only one server with Hub,Mail and CAS role installed. Also there is a Edge transport role installed in the perimeter network.
We are planning to purchase 2 brand new servers for Exchange DAG and hope to retire the old server after migrating completed My concern is that I've never done a Exchange Migration in this type of a setup where mix server OS and lower Functional level exists.
It would be great if you could let me know what should i look before planning this migration.
Are there any known issues of the current setup I need to be aware of while migrating?
Is there a complete guide available that I can refer?
Please be kind enough to support me to find accurate information to plan and execute this migration.
Thanks in advance.
Tharaka

Hi Tharaka,
In addition to Steve's suggestion, I would like to clarify the following thing:
When you migrate Exchange 2007 to Exchange 2010, you need to stand up the new environment, create a 'legacy' name space (or rename 'owa' is an option), and then move mailboxes to the new environment.
Here is a thread about migration from Exchange 2007 to Exchange 2010 for your reference.
migration of exchange server 2007 to 2010
http://social.technet.microsoft.com/Forums/en-US/0d0d031d-46ed-4806-ada5-6590346caa74/migration-of-exchange-server-2007-to-2010?forum=exchangesvrdeploylegacy
What's more, about Exchange 2010 DAG, here are some helpful threads for your reference.
Database Availability Group Design Examples
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
Understanding Database Availability Groups
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

2 Problems after migration Project Server 2007 to 2010

Hi Everyone!!
I have 2 issues after migrate MS Project Server 2007 to Project Server 2010, in fact i had a lot issues, but i can solve almost all, so after solve all issues, just is pendings 2 issues very rare:
Backgrounds:
Migrated from: Windows Server 2008R2 - SQL Server 2008 R2 - Proejct Server 2007 with WSS 3.0 - All updates are up to date (CU is up to date) and all platform is ok
To: Windows Server 2008R2 - SQL Server 2008 R2 - Project Server 2010 SP2 - SharePoint Server 2010 SP2 - All updates are up to date (CU is up to date) and all platform is ok
3 Servers in the Farm, ----> 1WFE-1WAPP-1DB
Issues:
In the Project Center, some migrate Project don't show the icon with image about project documents, risk and issues although that project effectively have documents , risk and issues
In "Server Settings" , in section "Operational Policies" in "Project Sites" almost all projects don't show the URL with Project Site
For the issues 1 and 2, i tried some things:
Re publish all projects (approx 700 projects) with a script via PowerShell available in technet
Run the Wizard Again
Rebuild Solution
Restart the all Servers in the Farm
Restart Services ----> IIS - Project EventService - ProjectQueue - SharePoint Timer
and i can't solve it yet!!!
Please Any Ideas?
Erick Gutiérrez PMI Membership #ID 2089740 MTCS - Microsoft Project Server Managing Projects

Have you restored content DB successfully?
for point 2 have you performed:
have you synchronized project site under server setting --> operational policies --> Bulk Update Project
Sites
http://pwmather.wordpress.com/2012/10/08/projectserver-2010-bulk-update-project-site-issue-ps2010-msproject-sp2010-sharepoint/
after doing this publish all the project which are having issue it may solve your 1st issue.
You can check if below condition is applies to you (PWA 2007)
You may need to use the WSS site re-linker tool –
now built in to Server Settings in PWA as “Bulk Update Project Sites”. If you have changed URL die to a different port then re-linking should get your sites in order. In upgrade scenarios the “Previous Site Path” Web application might show as a GUID
in the drop down – however it still works and will re-link the sites.
http://technet.microsoft.com/en-us/library/cc197498(v=office.12).aspx
kirtesh

Steps to migrate Project Server 2007 from SQL Server 2005 to SQL Server 2008?

We need to migrate Project server 2007 from SQL Server 2005 to SQL Server 2008.
1. Is it as simple as doing backup and restore of databases and pointing Project Server to the new DB server? Or there are some specific steps that should be followed?
2. Article at
http://technet.microsoft.com/en-us/library/dd207290(office.12).aspx is about moving databases from one DB server to another (same versions). At one place, it mentions to
backup all databases but at another place it mentions that
You should only back up the Draft and Published databases from the source database server.
What should be done when moving from 2005 to 2008?
Regards,
Amit
Gupta

High Level step you can get this form Tech net or MSDN too
Shut down the SharePoint servers (App / Web)
backup all of the SharePoint and Project
Server databases from the SQL 2005 server
copy these over to the new SQL 2008 server and restore all of
the databases with the same names
script out all of the logins used by SharePoint/PS from the SQL 2005 server and create these on the SQL 2008 server
script out the Delete expired sessions SQL job from the SQL 2005 server and create this on the SQL 2008 server - or create them manually on the SQL 2008 server
repoint the SQL server DNS Alias from the SQL 2005 server to the SQL 2008 server, if SharePoint and Project Server was installed using the actual SQL server name and no alias, you can create a DNS alias for the old SQL 2005 server name that points to the SQL
2008 server. This is so that the SharePoint servers can still connect to the same SQL server name
Start up the SharePoint servers
kirtesh

Migration of Unity users from MS Exchange server 2007 to 2010

Hi,
I am having Unity 7.0 with MS Exchange server 2007,now want to transfer the users and Unity mailboxes to MS Exchange server 2010. Want to know the procedure. Can anyone help me out?

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365. That's hardly a trivial task. If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Please Help!! Lists and libraries suddenly blocked just before migrating from SharePoint 2007 to 2010

Hi all,
I took several weeks preparing the migration of a large farm from SharePoint 2007 to 2010 using the system of restore databases and mount site collections. I've built the new farm and I have done several full migration tests to verify that all was well the
day of final migration.
The farm consists of three virtual servers: one with SQL Server 2012 and two with SharePoint Server 2010. Upon completion of the tests we've moved the servers to another network. We have turned on the servers and everything seems to work fine.
Just the day of the final migration I wanted to check the HealtReports list of the Central Administration, and when I wanted to look up an alert, the view window has not shown me anything and ribbon has appeared with all options grayed. Days ago worked fine.
Alarmed by this, I have started to check all lists and libraries in the Central Administration and the same happens. I can not view or change the items, nor add. Neither I can change the properties of the lists or libraries, as if everything was locked. I
tried on the main site collection and same thing happens, and I have tried with several user with Total Control permissions. I have also verified that the site collection was not in ReadOnly mode.
I have restored a site collection from SharePoint 2007 and have migrated successfully to 2010. Before applying visual upgrade I found that the content is also locked. It is as if he had changed anything in the configuration of the whole farm, but I can not
find what. The Event Viewer of the three server shows no errors related to this. The SharePoint LOGS not show anything unusual.
I do not know where to look and urges me to find a solution because the old servers must be out of service soon. I accept any suggestions.
Kind regards.

Finally I answer myself because I've already found and fixed the problem. Before moving the servers in farm to the another network I've unplugged the single SharePoint server from the farm database for to clone it. Apparently
this disconnection removes all the implemented solutions and the farm remains without servers. Reconnecting the servers not re-implements the solutions. When I was about to create a new farm I have seen that all solutions were not implemented,
I have implemented one by one and the system worked again.
If any of you happen reaches you, now you know what it may be due.
Kind regards!! Now I'm a happy man! ;)

After the in place upgrade from SharePoint server 2007 to 2010, the out of the box approval workflow does not prompt for additional information after check in of a major version.

I think it has to do with the interaction between Word, InfoPath, IIS, and /or SharePoint, but I cannot put my finger on it. Maybe client integration or authentication settings? I have looked at it in wireshark
and have not seen anything glaring.
Steps to reproduce the (working) behavior:
Set up a document library in SharePoint 2010.
Under versioning settings, make the following changes:
Set Require Content Approval for submitted Items to Yes
Select Create Major and Minor (draft) versions
Set require checkout to Yes
Create an out of the box “approval” workflow with the following settings:
Start this workflow to approve publishing a major version of an item.
I then create a new document. Save it. check it in. it is now version 0.1.
I then open it again. check it out. Make a change. Close and save it.
Check it in.
Publish major version:
At this point a screen is presented to me to enter workflow parameters. This screen comes up in Enterprise 2013 and MOSS 2007, but not the migrated version of 2010:
This is what I need help with. It should come up in 2010. To fix it in 2013, I had to change the IIS bindings to only have 1 entry for a port. I did this for 2010 and it did not work.
Any help or ideas is very appreciated. Thanks very much in advance.

Hi Chris,
According to your description, my understanding is that the approval workflow cannot work when the workflow was set to start to approve publishing a major version of an item after upgrading to SharePoint 2010.
I recommend to check the approval workflow in Workflow settings of the corresponding library to see if the Start this workflow to approve publishing a major version of an item is checked.
For test, I recommend to create a new OOB approval workflow and set it to start to approve publishing a major version of an item in the same library to see if the workflow can work.
Thanks
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Removing mailbox server from Exchange 2010 DAG - Node not fully cleaned up

Hi,
We are in the process of decommissioning some old Exchange 2010 servers. I have just attempted to remove one of our mailbox servers and have received a number of errors, related to its removal from the DAG.
I have already removed the Public Folder replicas and all mailbox database copies. I then tried to evict the server from the DAG and received the following warning:
I then ran the command that was recommended, from another server and in an administrative command prompt:
I have looked in this log on both the server I ran the command on, a CAS server, and the mailbox server itself and can see no evidence of this error 2 that is listed here.
If I run the Powershell command to look at the DAG I cannot see it there any more. I am assuming that this error message might only be an issue if I was planning on re-using this server somewhere else in Exchange or perhaps adding this server to another
DAG. But I just want to decommission it.
Can anyone put my mind at rest as to whether this is a genuine concern or not. If not my next step is to uninstall Exchange 2010 from this server and turn it off.

Hi Belinda,
I get the following:
[PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
Name Member Servers
Operational Servers
DAG01 {WSR-EX-01, WSR-EX-101, WSR21}
It doesn't look like that server is part of the DAG any more as far as I can see. I just can't explain that error message reported from the cluster command. As far as I can see the server is isolated. I already removed its database copies as a pre-requisite
before removing it from the DAG as per this guide:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27039933.html
I found a nice little script that gave reports on your Public Folder configuration and it highlighted that some of our folders were not being replicated properly across our mailbox servers. This helped me in removing these services from the server.
It is currently doing nothing at this time as far as Exchange Services are concerned.

Project Server Error Event ID 6971 when upgrading from Project Server 2007 to 2010.

Hi All,
I get the following error when trying to import a project server site from PS 2007 to PS 2010. The error occurs after the provisioning is completed. The initial error with event id 7381 is:
"ProjectSite post provision setup completed with errors"
This error is followed by Event Id 6971 and the following error text. I checked the site and I do see the sub sites under the main project server site, but the actual PWA site is not created and integrated with the project server components. The
database upgrade of all the 4 Project Server databases went through ok. I am not sure how to fix this problem. Any help that you guys can provide is great appreciated.
Failed to provision site "Testsite "with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Membership synchronization failed. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.InitWebPublic()
at Microsoft.SharePoint.SPWeb.get_Language()
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.DeleteRoles(SPWeb web)
at Microsoft.Office.Project.Server.BusinessLayer.SharePointSecurityHelper.ConfigureDefaultPWAWSSSecurityModel(SPSite topSite, SPWeb web)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.<>c__DisplayClass18.<QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces>b__17()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.QueueUpdateUsersAddRemoveStatusOnPwaRootsAndWorkspaces(Dictionary`2 deletedUserUidsLoginNames, Guid[] addedUserUids, Boolean isFullSync, Boolean syncWorkspaces)
at Microsoft.Office.Project.Server.BusinessLayer.Admin.SynchronizeMembershipForPwaAppRootSite()
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.SynchronizePwaMembership(ProjectProvisionSettings provset, ProjectSite projectSite)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)
Thanks,
Anand.

Hi Anand,
Thanks for the info.
Basic rule for DB attach method is, we should not change Project Web Application site collection name. E.g of old site was /PWA , when we move databases from one farm to another site should
be provisioned as /PWA. Brian Smith's excellent blog article can help you to understand common issues
As per the error message posted earlier, looks like you are trying to provision PWA site as “Testsite”
Correct me if I am wrong
http://blogs.msdn.com/b/brismith/archive/2011/02/07/project-server-2010-common-project-web-app-pwa-provisioning-problems.aspx
Verify that you are not using one of the reserved outline code or custom field
http://technet.microsoft.com/en-us/library/ee662500.aspx
Custom field and lookup table name conflicts
Hrishi Deshpande – Senior Consultant DeltaBahn
Blog | < |
LinkedIn
Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

Bulk Project Site option isn't working in project server 2010 migrated from PS 2007.

Hi,
I am doing a test migration from epm 2007 to epm 2013.
So first, i need to migrate the project server 2007 to project server 2010. i have 2 separate environments for EPM 2007 and EPM 2010).
there is no problem in migration process and i successfully migrate entire PWA 2007 to 2010, except Workspaces (Project sites).
Bulk project site option is not helping. I have tried 4-5 times with different PWA 2007 databases (PWA1, PWA2...) but this option did not work. and errors in queue are WSSWebDoesNotExist(16405) and GeneralQueueJobFailed(26000).
Then next time while migrating all over again i kept the same port and same PWA name then bulk project site option worked.
Question is, Do i need to keep the same PWA name and same port for the new upgraded PWA??, one more issue regarding this is that if don't keep the same PWA name and i open the project site and click on the "Project web app" back link, it
redirects me to old PWA site which doesn't exist and give me page not found error (Obviously).
Below, you can see the both scenarios.
my previous PWA 2007 site, say - http://epm2007:2222/PWA
When - migrated PWA 2010 site, say - http://epm2010:3000/NewPWA (Bulk project site update just doesn't work)
When - migrated PWA 2010 site, say - http://epm2010:2222/PWA (Bulk project site update worked)
Whats the solution of this problem. is there any utility or query to link all project sites correctly?
Will i face the same problem while migrating PS 2010 to PS 2013??
Thank you.
sandeep

Hi,
I would say it is easier to keep the same PWA name between 2007 and 2010 (no need to have the same port).
If you want to move to a new PWA URL maybe you can use stsadm backup/restore as detailed in this article?
http://technet.microsoft.com/en-gb/library/ee662500(v=office.14).aspx
Hope this helps
Paul

Project Server Migration from 2007 to 2010

Hi Team,
I am migrating project server 2007 and wss 3.0 to sharePoint 2010 and project server 2010. I am using full database attach upgrade method. The provisioning process end up with failure and uls logs showing the below mentioned errors.
ULS Logs can be found at the below mentioned link
https://onedrive.live.com/redir?resid=AC01B07FAACAFC5!534&authkey=!AM1v2WSkbUQx-t8&ithint=file%2ctxt
I am looking for help, and i really appreciate if some one can help me sorting this out.
Regards
Kashif
Kashif Saeed

um...
> Upgrade session finished successfully! 0 errors and 0 warnings encountered.
not sure what you're asking
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Migration from Exchange 2007 SP3 to Exchange 2010

Hello,
We are planning a single server migration from Exchange 2007 SP3 to Exchange 2010. I'll be building the 2010 server on a 2008 R2 box. My question is, can I make the jump directly to Exchange 2010 SP3, or do I need to install exchange 2010 SP1 first
- migrate from 2007 SP3, and then install SP3 for exchange 2010 later?
Thanks,
Eric

@ Hasan
Dimdik - TAT,
That's not correct at all, you can migrate exchange server 2007 SP3 and RollUp Update 10 minimum to Exchange Server 2013 with minimum CU1.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Sharepoint 2007 to 2010 Migration issue

Hi Techies,
I am doing migration from sharepoint 2007 to 2010,
I have restored the 2007 content DB to 2010 server,But the problem is during attachment of content DB to sharepoint 2010 web application,I am getting the database upgradation issue.
Please help to solve this issue.
Thanks Regards,
Simanchal Padhi

Hi Simanchal,
Could you please let me know what exact error you encountered while attachment of content DB?
By your question, I understand you are facing a database upgrade issue.
Have you run below command before you ran Mount-SPContentDatabase
command?
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Please remember to click 'Mark
as Answer' if the reply answers your query or 'Upvote' if it helps you.

Migration from 2007 to 2010 - AD issue

Hi,
I'm currently migrating from EPM 2007 - EPM 2010 with a great handicap,
the source AD "source-ad.com" its not the same at destination "destination-ad.com"
Can I commit the migration, changing the "source-ad\user01" account resources, to "destination-ad\user01"?
I assume that the account name are the same between "source-ad" and "destination-ad.com"
Thanks in advance,

Hi
Below article has the steps to migrate the project server from one domain to another.
http://blogs.msdn.com/b/brismith/archive/2009/06/22/project-server-2007-migration-from-one-domain-to-another.asPx
If you are looking to Migrate the Project server between domains and also migration of project server from 2007 to 2010, then it is best to migrate the Project server from one domain to another domain first and then migrate it from 2007 to 2010.

How to Migrate MS Project Server 2007 to 2013

Hi
Can any one share some reference for migrating Project Server 2007 to 2013.
As in general process--
We can take the backup and and restore it in 2013 environment.
How to migrate Portfolio Server?
After restroring any steps need to be followed.
Please guide.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

Hello,
For Portfolio Server 2007 options, review this guide:
http://www.microsoft.com/en-us/download/details.aspx?id=20815
Also see:
http://blogs.technet.com/b/projectadministration/archive/2010/07/21/anouncing-project-portfolio-server-2007-migration-documentation-to-project-server-2010-just-released.aspx
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Unable to save/publish Projects on Project Server 2010() using Project Pro 2007 and 2010

Hi,
Recently we have upgraded from Project Server 2007 to 2010 SP-2 (BCM enabled) environment and from last few days we are getting issue with Project Plans where PMs are not able to update Projects means save and publish the Project using MS Project 2010/2007.
Whenever PMs try to open project using MS Project 2010 SP-2, it gets load successfully but when they hit save and publish no jobs are getting fired up nothing is happening. Only way to get out from MS Project 2010 window is to close the Project window and
and click discard changes. No error and exception windows are popping out in MS Project 2010, no error/problem/issue clue at all from MS Project 2010.
But when I try to update this Project plan for very first time using MS Project 2007 Sp-2 then I am getting below error
for any subsequent save and publish using MS Project 2007-SP2 getting below error
As an alternative I have tried to open this Project Plan using web and there it is getting opened saved and published successfully from PWA absolutely no issue.
Also I have saved this Project locally as XML and saved and published it on Server successfully. But after someday again this project got corrupt PMs started getting same problem again
I have also looked at ULS logs but not getting anything useful there.
So any guesses why this could happen that can give me pointers to find actual root cause, please let me know.
Thanks much !!!
Sachin Vashishth MCTS

Used below steps to fix the Projects on MSP 2010.
1) Open corrupted project in MS Project connected to PS 2010 Prod env.
2) Goto > Resource > Add Resource > Build Team From Enterprise
3) Check is there any local resource who has not replaced with corresponding enterprise resource. If yes then replace all those local resources with enterprise resource. If not then move to next step.
4) Open resource sheet view and sort or filter by local resources.
5) Then add few columns in resource sheet view like "Windows User Account, Email Address , Base Calendar etc".
6) Now check has any local resource having enterprise attribute assigned to it, if yes then delete or assign local value as appropriate.
7) Then GoTo > File > Save & Send > Save as project file > Save for sharing (at local location)
8) Close project plan window and click "Yes" to save changes.
9) Restart MS Project 2010 and open your project from local location.
10) Then Goto > File > Save & Send > "Publish to Project Server". This will open "Import Project Wizard" to validate Resources and Task in Project.
11) Then in Import Project Wizard window at left hand side click "Map Resource" to validate project resources.
12) This will "Map Project Resource to Enterprise Resource " check all the resources highlighted with "Red" font and map "Standard" calendar to local resources.
Note: Don't worry about local resource assigned "Standard calendar" but still highlighted "Red".
13) Then click "OK" and click on "Continue to step 2" at bottom of "Import Project Wizard".
14) Make sure you get number of errors 0 in step 2, else click on validate resource and take proper corrective action as explained in step 6.
15) If you leave at least one resource as a local resource (unmapped to an enterprise resource), you will see the local resource in the Import Resource grid on the right side
of the Confirm Resources page.
Examine the value in the "Import" column (if not able to see this column then insert this as new column) for the local resource .
The default value is "Yes", then change the value in the "Import" column
to "No", else system will import the local resource as an enterprise
resource.
16) Then "Continue to step 3, 4 and 5".
17) Then at Step 5 , Save project to Project Server by clicking "Save as" link.
18) Then publish the project to update the plan at PWA 2010.
Sachin Vashishth MCTS

Migrating Exchagne Server 2007 to 2010 DAG....

Similar Messages

Maybe you are looking for