RE: SBS 2003 migration blues

HI Samudra,

Thanks for detailed updates.

If the issue occurs on the comanyweb and after you reinstall the intranet
components the issue still exists, we have to do a completely reinstall of
companyweb, you can follow the steps below:

I. Rename the registry keys and folders:

1. Rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
2. Rename Program Files\Microsoft Integration\Windows Small
Business Server 2003 (If you are in the middle of RC to RTM upgrade, rename
Program Files\Microsoft Integration\Windows Small Business Server
2003\Release Candidiate instead)
3. Rename Program Files\Microsoft Windows Small Business Server
4. Verify Program Files\Windows for Small Business Server exists on
the server. If not, you need to send him a copy of the folder from your SBS
2003 server. (Or you can manually rebuild the files from CD1\Setup\i386)

II. Once we rename the registry keys and folders, SBS setup is going to be
running like the first time.

1. Insert SBS setup CD 1, and then run setupsbs.exe to rerun the
setup.
2. In the ''Component Selection'' page, make sure ''Server Tools''
and all the sub-components (including ''Intranet'') are selected to
INSTALL.
3. Once it is completed, click Start, click Control Panel, and then
click Add or Remove Programs.
4. Select Windows Small Business Server 2003 and then click
Change/Remove. The Setup Wizard appears.
5. Click Next to start the wizard.
6. On the Windows Configuration page, click Next.
7. On the Component Selection page, in the Action column, change
Server Tools to Maintenance, change Intranet component to Remove, and then
click Next.
8. On the Component Summary page, click Next.
9. Click Finish.

10. Uninstall Microsoft SQL Server Desktop Engine (SHAREPOINT). In Add
or Remove Programs, select Microsoft SQL Server Desktop Engine (SHAREPOINT)
and then click Remove. A dialog box appears. To confirm that you want to
remove, click Yes.


III. Delete Registry Keys:

1. Delete
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Intranet
2. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SHAREPOINT
3. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web
Server Extensions\Ports\Port /LM/W3SVC/4: (Do not delete "Port
/LM/W3SVC/1:" because it is FrontPage Server Extension 2002 which is
installed on the Default WebSite. If you see additional "Port
/LM/W3SVC/X:", backup and then remove them)


IV. Delete IIS Virtual Directory:

1. Delete SharePoint Central Administration (Do Not Delete
Microsoft SharePoint Administration. It belongs to FronPage Server
Extension)

2. Delete Companyweb

Note: If AV software install any extra IIS virtual directory, also remove
them if possible. They sometimes use port 8081 which will conflict with our
SharePoint Central Administration virtual directory.

3. Delete Application Pool

There should be only 4 application pools (DefaultAppPool,
ExchangeApplicationPool, ExchangeMobileBrowseApplicationPool, and
MSSharePointAppPool). Besides those 4, delete all extra.


V. Rename Folders:

1. Rename C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT
2. Rename C:\Inetpub\companyweb

NOTE: Location of the MSSQL$SHAREPOINT folder is determined by
HKLM\Software\Microsoft\SmallBusinessServer\Monitoring\MSDE_Location. Check
out this registry key and determine the real location of the folder.

VI. Clear the contents of the %temp% folder. If you are not able to clear
the contents then reboot the server or reboot into safe mode. Other
contents to clear would be in the c:\program files\Microsoft
Integration\Windows Small Business Server 2003\Logs everything inside of
the Logs folder.

Then do the following steps.

VII. Install the intranet component:

1. In Add or Remove Programs, select Windows Small Business Server
2003 and then click Change/Remove. The Setup Wizard appears.
2. Click Next.
3. On the Windows Configuration page, click Next.
4. On the Component Selection page, in the Action column, change
Server Tools to Maintenance, change Intranet component to Install, and then
click Next.
5. On the Logon Information page, click Next.
6. On the Component Summary page, click Next.
7. Click Finish.



VIII The Installation should still fail, then apply the patch located at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=CB7E90A1-DE9D-4A83-
85F8-951E9F055BF0&displaylang=en


IX. If companyweb still doesn't work, open up a command prompt and
navigate to the directory ''C:\Program Files\Microsoft Windows Small
Business Server\Client Experience\Provision'', and then run the following
commands:

Note: It may take several minutes for this installation to complete; it is
a silent command. You can bring up task manager and look at the process
graph, when it stabilizes, it should be done.

stsprovision -path C:\Program Files\Microsoft Windows Small Business
Server\Client Experience\Provision -oeminstall -exch

stsprovision -path C:\Program Files\Microsoft Windows Small Business
Server\Client Experience\Provision -install -exch

Please carefully follow the steps below to reinstall the companyweb to see
if the error can be cleared. I will be here waiting for your updates.




Best regards,

Charles Yang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: SBS 2003 migration blues
| thread-index: AcX0GG7wANa9wYRKQgmci8TCw+TNtg==
| X-WBNR-Posting-Host: 222.13.11.58
| From: "=?Utf-8?B?U2FtdWRyYQ==?=" <Samudra@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <35795D03-0EB6-4C6E-BBA9-48E9AC243103@xxxxxxxxxxxxx>
<7S7#VT88FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: SBS 2003 migration blues
| Date: Mon, 28 Nov 2005 04:37:02 -0800
| Lines: 175
| Message-ID: <D5C19B60-429D-431A-ACAD-E770918CC6AE@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:226012
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Dear Charles Young,
|
| Thanks for your post in response to my query on SBS2003 Migration blues.
|
| Further to my earlier post, please note that after I did the migration,
| users can logon to the server, check their exchange mails and use their
| Internet connection through the server. Unfortunately, the Intranet
| (http://companyweb) is not working. It is also affected the backup
| monitoring pages, which is also not accessible. I guess, all these are
| happening due to the intranet failure. The users can see the
| http://companyweb, but can not access the buttons, "CREATE" or SETTINGS".
| Similarly, another website created at
| http://companyweb/sites/brookeconsulting (this is the site required to be
| migrated), users can see the information there and can add documents or
| change dates etc., but unfortunately they can not "Modify the settings"
like
| changing the number of columns etc. It always comes out with a '/_layout'
| error page. I re-installed the companyweb, yet the same problem persists.
|
| Also on top of that, now I can not even get the old brookeconsulting site
up
| and running by restoring it from the SBS backup.
|
| Please let me know, which logs will help you to understand the problems
in
| detail. I will then send those in my next mail.
|
| With best of warm personal regards,
|
|
| Samudra Dutta Gupta
| Tokyo, Japan
|
|
| ""Charles Yang [MSFT]"" wrote:
|
| > Hi Samudra,
| >
| > Welcome to SBS newsgroup.
| >
| > I am sorry for the delayed response due to weekend. Please understand
that
| > the newsgroups are staffed weekdays by Microsoft Support professionals
to
| > answer your systems and applications questions. Your understanding is
| > greatly appreciated!
| >
| > Issue description:
| > ============
| >
| > I understand that none of the exchange related AD accounts did not
migrate
| > when you follow the migration white paper.
| >
| > Analyzing and suggestion:
| > =============
| >
| > Generally speaking, the SBS migration tools ADMT only migrate the
account
| > to the ADUC to another SBS server. For the exchange related mailbox, we
| > need to migrate it via exchange migrate wizard and connect it via the
| > accounts on the new SBS 2003, please follow my steps below:
| >
| > 1. As I know, if you strictly follow that article, you will find all
the
| > migrate accounts to the OU you specify, not just on the ADUC accounts,
the
| > SBS have special OU for the user created via wizard, you will find the
user
| > accounts on the following OU:
| >
| > MyBusiness\Users\SBSUsers
| >
| > 2. If you want to migrate the mailbox, please refer to the KB article
| > below, also as I know the migration white paper describe it clearly on
the
| > exchange mailbox migrate section:
| >
| > 328871 How to use the Exchange Migration Wizard to migrate mailboxes
from an
| > http://support.microsoft.com/?id=328871
| >
| > 3. For the sharepoint issue, we are not clear about the detailed
problem
| > you encountered, we want to know have you rerun the CEICW to make sure
the
| > sharepoint services run well, please also check the event view to paste
any
| > sharepoint related error message to newsgroup.
| > 4. Do you encounter any problem when accessing the companyweb?
| >
| > I appreciate your understanding on this issue; please feel free to post
| > back the results. I am glad to be of assistance.
| >
| >
| >
| > Best regards,
| >
| > Charles Yang (MSFT)
| >
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| >
| > ======================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > ======================================================
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| > =====================================================
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > =====================================================
| >
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Thread-Topic: SBS 2003 migration blues
| > | thread-index: AcXy5e9f+d+vQKvlS9aWRU3QwboyEQ==
| > | X-WBNR-Posting-Host: 222.226.9.254
| > | From: "=?Utf-8?B?U2FtdWRyYQ==?=" <Samudra@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: SBS 2003 migration blues
| > | Date: Sat, 26 Nov 2005 16:03:02 -0800
| > | Lines: 18
| > | Message-ID: <35795D03-0EB6-4C6E-BBA9-48E9AC243103@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:225711
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Hello all,
| > |
| > | I do not know whether its right to mention here. I tried using the
| > Microsoft
| > | domain knowledgebase article to do a migration, sbs2003 to a
different
| > | hardware (original source was a migrated SBS 2003 from sbs 2000 but
was
| > | working fine). But while ADMT worked fine, Exchange Migration tool
asked
| > me
| > | to create a new set of users, which the tool itself was creating
putting
| > | %oldusername%1 after all available user names, and did the migration.
| > After
| > | that, I disabled the originally ADMT migrated accounts and started
| > working
| > | with the new users created by the exchange 2003 migration tools and
no
| > | problems EXCEPT Sharepoint Services. I can no longer use the "Site
| > Settings"
| > | button or "Create" button for the topmost site that I created for
this
| > | migration. I tried various things, and found that the exchange server
| > created
| > | accounts are showing up on the Administrative Tools --> Server
Management
| > -->
| > | Users list but not on Administrative Tools --> Active Directory Users
and
| > | Computers list. This last list only contains the ADMT migrated
accounts,
| > | which were disabled by me, as it does not have any mail files
associated
| > with
| > | them. Any help will be greatly appreciated.
| > |
| >
| >
|

.