RE: Cannot access companyweb
- From: v-chacez@xxxxxxxxxxxxx (chace zhang)
- Date: Tue, 15 Aug 2006 04:30:43 GMT
Hi,
Thanks you for posting here.
From your description, I understand this issue is: Using KB 884453 "How toinstall Small Business Server 2003 in an existing Active Directory domain"
to migrate from SBS 2003 to SBS2003, in this period, you can't achieve this
goal due to specific reason and posted it back, currently you can not
access companyweb and in IIS console he encountered "IIS was unable to
start this site. Another site may already be using the port you have
configured for this site. Please select an unused port for this site".
First I want to emphasize we do not recommend customer use this article to
add an SBS 2003 computer to a network where there is an existing SBS 2000
or SBS 2003 domain controller for migration purposes.
Based on my experience, please re-run CEICW wizard to configure your SBS
Server.
More info please refer to following MS knowledge base article:
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763
To do so:
1. On the Small Business Server 2003 computer, click "Start", and then
click "Server Management".
2. Expand "Standard Management", and then click "To Do List".
3. In the right pane, click "Connect to the Internet", and then click
"Next".
4. On the "Connection Type" page, click "Do not change connection type",
and then click "Next".
5. On the "Firewall page", click "Enable firewall", and then click "Next".
Important Do not click the "Do not change firewall configuration" option.
6. If you receive the following message, click "OK":
To ensure the proper configuration of ISA Server, existing custom packet
filters will be disabled. For information on how to re-enable existing
packet filters, see Small Business Server Help.
7. On the "Services Configuration" page, click to select the check boxes of
the additional services that you want to make available from the Internet,
and then click "Next".
h. On the "Web Services Configuration" page, click "Allow access to only
the following Web site services from the Internet", click to select the
check boxes of the services and of the Web sites that you want to make
accessible from the Internet (i.e. Outlook Web Access, Remote Web
Workplace, Outlook Mobile Access, Outlook via the Internet, Business Web
site (wwwroot), etc.), and then click "Next".
8. On the "Web Server Certificate" page, click "Create a new Web server
certificate", type the Small Business Server computer's fully qualified
domain name in the "Web server" name box, and then click "Next".
[Important] The fully qualified domain name that you type in the "Web
server name" box must be the same name that you use to connect to the Web
site from the Internet. For example, if the URL that you use to connect to
a Microsoft Outlook Web Access Web site is
<<https://external.domain.com/exchange>>, type "external.domain.com"
(without the quotation marks) in the "Web server name" box.
Note: If you don't have your own registered fully qualified domain name
(FQDN), we can input the "Public IP Address" (As you mentioned the [valid
IP address]).
9. On the Internet E-mail page shows, select "Enable Internet e-mail" and
click Next.
10. Select either "Use DNS to route e-mail" or "Forward all e-mail to
e-mail server at your ISP". If you select the latter, enter the ISP SMTP
server. Click Next.
11. Specify to receive e-mail using one or both of the following methods:
- POP3 Mailboxes
- Exchange
Click Next.
12. Enter your e-mail domain name and click Next. The e-mail domain name
should match the mail exchanger (MX) resource record maintained at your
ISP. This must be a registered Internet domain name.
13. Go through the steps to finish the wizard.
14. On the "Completing the Configure E-mail and Internet Connection Wizard"
page, view the configuration information to make sure that it is correct,
and then click "Finish".
For your convenient, I provide following info of migrate SBS Server 2003 to
a new hardware.
there are three method to move the SBS 2k3 to new hardware. I listed them
as following as well as their main features.
1. A disaster recovery method
By this method, you need to manually restore Exchange data, SharePoint
Data, contents in Users shared folders. This method can complete rebuild
the same server on new machine.
2. FSMO Role transfer method
By this method, you need to use a standard version of Windows 2003 as
interim.
3. A third-party method
The steps on http://www.smallbizserver.net/DesktopDefault.aspx?tabid=99 are
detailed; however, we still recommend you do a backup prior to beginning.
In case the procedure fails, we can restore the System to the original
status. Since it is a third-party method, the suggestions on it are not
officially supported. As my personal experience, it is easy to follow and
efficient.
Now, I will list the detailed steps to 1 and 2 methods. Please refer to it.
I. Disaster Recovery
Backup: If you do not have a good backup of your original server, please
follow the backup steps to backup the server data.
1. Open ''''Exchange System Manager'''', navigate to
''''Servers''''\<Server Name>\''''First Storage Group''''\''''Mailbox
Store''''. Right-click it and choose ''''Properties''''. In the properties
window, click ''''database'''' tab. Write down the path of the database
file and streaming file. Also check the path of the public folder database
files.
2. Open ''''Services'''' console in ''''Administrative Tools''''. Stop
''''Microsoft Exchange Information Store'''' service. If the exchange
database files are stored in the default path (c:\program
files\Exchsrvr\mdbdata\), open Windows Explorer, navigate to the Exchange
database folder, and then save the .edb files and .stm files to a folder on
another disk partition or a shared folder on a internal workstation
3. Open Windows Explorer. If ''''Users Shared Folders'''' is on C:\ drive,
copy it to another disk partition or a shared folder of on a internal
workstation.
4. If you are using the SBS 2003 built-in SharePoint site (Companyweb), you
may refer to the following KB article to move the database file:
827701 How to perform a disaster recovery operation of SharePoint Services
http://support.microsoft.com/?id=827701
5. Backup other data which you want to restore to the new installation.
Restore:
1. Insert SBS 2003 CD#1 into the CD driver. Boot the machine by using the
CD-Rom. Install SBS 2003 server. (Format original system drive)
2. Create new user accounts (duplicate the original accounts) by using Add
Users Wizard.
3. Open Services Console, stop ''''Microsoft Exchange Information Store''''
service. Open ''''Exchange System Manager'''', navigate to
''''Servers''''\<Server Name>\''''First Storage Group''''. Right-click it
and choose ''''Properties''''. Select the database folder. (The original
database files should be copied to this folder).
4. Open Exchange System Manager. Navigate to ''''Servers''''\<Server
Name>\''''First Storage Group''''\''''Mailbox Store''''. Right-click it and
choose ''''Properteis''''. Click ''''Database'''' tab and check ''''This
database can be overwritten by a restore'''' option. Also check this option
for ''''Public folder store''''.
5. Open Services console, start ''''Microsoft Exchange Information
Store'''' service. In Exchange System Manager console, right-click
''''Mailbox store'''' and choose ''''Mount Store''''. Also mount the public
folder store.
6. In Exchange System Manager console, expand ''''Mailbox Store''''.
Right-click ''''Mailboxes'''' folder and choose ''''Run Cleanup Agent''''.
After doing this, you will see the mailboxes with red crosses in the right
panel. Right-click each mailbox and choose ''''Reconnect''''. Connect the
mailboxes to the current user accounts.
7. Restore the contents in Users shared folders.
8. Follow the KB 827701 to restore the SharePoint site.
The above steps will help you reinstall the SBS 2003 server. To preserve
client user profiles and settings that was on the original domain to the
new SBS 2003 installation, a manual way is documented in the KB article:
314045 HOW TO: Restore a User Profile in Windows 2000
http://support.microsoft.com/?id=314045
Another way is to create a local profile, copy the original domain profile
to the local profile, and then let the "Setup Computer" wizard do the task
"map local profile to new domain profile" for you.
As long as you create your computer accounts using the server manager''''s
"to do list" you will be prompted to migrate profile information. When you
join the workstations to the domain by using the web site (ie
http://servername/connectcomputer) part of the process of joining the
domain will allow you to migrate user settings. However, to use this
method, you need to make sure that the profile you want to migrate from is
a local user profile (Not a previous domain profile):
1. Before joining the client to SBS 2K3 domain, create a local profile, and
then copy the old domain profile to a local profile.
2. Add the SBS Server into the network
3. Use the Setup Computer Wizard in SBS 2003 to join the (now) XP Pro
machines to the SBS domain: Server Management, Standard Management, Client
Computers, Set Up Client Computers.
4. On the client, access http//<Server name>/connectcomputer to bring up
the Setup Computer Wizard, it will then allow you to map domain user
accounts to local profiles on the machine thus preserving your profiles:
"Assign Users to this Computes and Migrate their Profiles".
5. You will Add a domain account to "Users assigned to this computer!/, and
then choose the existing local user profile in the "Current User Settings".
By Default, the value for "Current User Settings" is "None".
For the detailed steps, please refer to the following documents:
http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/bkuprcvr.mspx
http://download.microsoft.com/download/1/1/6/11671e4d-fb21-489c-870f-db36fd2
1a7d2/SBS_MoveDataFolders.DOC
Backing Up and Restoring Windows Small Business Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=487736f8-f6f5-436d-
a82d-0c8d66e2a634&DisplayLang=en
II. FSMO transfer method
0. Make a full backup of the SBS 2003 server.
1. Use Exmerge.exe on the SBS 2003 server to export all mailboxes to PST
files. To do so, you can refer to the following articles:
174197 XADM: Microsoft Exchange Mailbox Merge Program (Exmerge.exe)
Information
http://support.microsoft.com/?id=174197
327304 HOW TO: Use ExMerge to Upgrade to Exchange 2000
http://support.microsoft.com/?id=327304
273642 ExMerge Does Not Work Unless You Have Receive As and Send As
Permissions
http://support.microsoft.com/?id=273642
2. In Outlook at a client computer, create PST files and move all public
folders to the PST files as a backup.
3. Install Windows 2003 on the new server box (you should use a retail
version of Windows 2003 CD, not the SBS CD #1) and join in the SBS domain
4. Run DCPromo and set it up as additional domain controller in the SBS
domain. More info how how to do this:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/sbs/maintain/addsrvrs.asp
5. Transfer the roles from the old SBS install to the new server. More info
on how to do this:
255690 HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690
324801 HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801
255504 Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain
Controller
http://support.microsoft.com/?id=255504
6. Set the New Server as GC (Global Catalog Server). To set a DC as a GC,
you can follow the steps in the following MS Knowledge Base article:
816105 HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105
7. Remove Exchange attributes (not mailbox) from all users by choose the
Exchange Task in "AD User and computers". If you find that you only have
the three items (Delete Mailbox, Move Mailbox and Enable Instant
messages.), you can just ignore them. This step is only to make sure to
remove all other attributes you have configured for users.
8. Stop the Information Store service on Old Server to take the databases
out of use.
9. Stop DHCP on SBS 2003, install DNS (make it AD Integrated so that it
will replicate all DNS information from the SBS server) and DHCP on the new
Windows 2003 server and then configure the DHCP scope the same as SBS 2003.
10. Configure the new server to point to itself for DNS. Configure all the
client computers to point to the new server as DNS. If you are using DHCP
to issue DNS server settings, you should configure your new DHCP server to
reflect the changes.
11. After making sure the clients can successfully, open AD User and
Computers, connect to the new server and remove the SBS 2003 server account
from the Domain Controllers container.
12. Take the old SBS server offline
13. Insert SBS 2003 Disc 1 on the new server to run SBS setup until
finished (be sure the organization information for Exchange is *exactly*
the same as on the old server)
14. Run through your To Do List to get on the client add packs, configure
Internet connection, etc.
15. Apply service packs and patches so the new server will be at the same
update level as the old server
16. Use the exmerge.exe tool to import the mailboxes from the PST files.
For public folders, you can import them in from the PST files in Outlook at
the client side.
17. Use the backup restore procedure for Sharepoint service to move the
content dabase from old SBS 2K3 to new SBS 2k3. You can follow this article
829112 How to back up and restore http://companyweb data in Windows Small
http://support.microsoft.com/?id=829112
If you have further questions or concerns, please feel free to let us know.
Thanks for your time and I look forward to hearing from you.
Have a nice day
Best Regards,
Chace Zhang (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.
--------------------
| From: "ByrneDM" <DavidMByrne@xxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: Cannot access companyweb
| Date: 14 Aug 2006 12:06:13 -0700
| Organization: http://groups.google.com
| Lines: 47
| Message-ID: <1155582373.757480.326870@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 198.134.2.62
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1155582379 6992 127.0.0.1 (14 Aug 2006
19:06:19 GMT)
| X-Complaints-To: groups-abuse@xxxxxxxxxx
| NNTP-Posting-Date: Mon, 14 Aug 2006 19:06:19 +0000 (UTC)
| User-Agent: G2/0.2
| X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; .NET
CLR 2.0.50215),gzip(gfe),gzip(gfe)
| Complaints-To: groups-abuse@xxxxxxxxxx
| Injection-Info: p79g2000cwp.googlegroups.com; posting-host=198.134.2.62;
| posting-account=pDoMjg0AAACR6h7PKW9OOG2gxb_xn6jY
| Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!news-out.c
wix.com!newsfeed.cwix.com!newscon06.news.prodigy.com!prodigy.net!border1.nnt
p.dca.giganews.com!nntp.giganews.com!postnews.google.com!p79g2000cwp.googleg
roups.com!not-for-mail
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:289659
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi....
|
| I'm hoping someone can help me out getting access back to
| http://companyweb.
|
| Let me tell you what I've done. I'm working on a simple network with
| an existing SBS 2003 machine (called p3server with an IP address of
| 192.168.1.100). I followed the MS doc 884453, How to install Small
| Business Server 2003 in an existing Active Directory domain, to add
| another SBS (name p4server with IP address 192.168.1.99) to the domain.
| I went through the process of diverting all FSMO roles to the new,
| p4server, server and continuing with the SBS set-up. I should state at
| this point that I am aware you cannot have 2 SBS's on the one domain
| but I was intending on removing the old p3server at the completion of
| the set-up, just as described in the aforementioned MS document.
| However, the plans to put p4server on the network changed at the worst
| possible time and I was forced to reverse the set-up and remove the
| p4server from the network (I set all FSMO roles back to the p3server
| and ran a dcpromo on the p4server to demote it.
|
| All seemd okay; the network was back to pre-p4server performance.....
| except for the http://companyweb...... when trying to access it from
| any of the network client machines the now removed 192.168.1.99 server
| is queried. How do I get the workstations to point to 192.168.1.100
| again to access the http://companyweb ....... and does anyone know why
| this is happening?
|
| I had a look in Server Management on p3server (now the only SBS machine
| on the network). Under 'Advanced Management - IIS - servername - Web
| sites' I see the 'Default Web Site is listed as 'Default Web Site
| (stopped)' and 'Companyweb' is listed as 'Companyweb (paused)'. I did
| manage to re-start the 'Companyweb' site but when trying to restart
| 'Default Web Site (stopped)' I get a message saying
|
| "IIS was unable to start this site. Another site may already be using
| the port you have configured for this site. Please select an unused
| port for this site".
|
| I'm not even sure if this has anything to do with the issue I'm
| experiencing, but it might be information enough for someone out there
| with more knowledge than me to enable them to guide me in the right
| direction?.... well, here is hoping! Anyone know how to get the client
| systems to point to p3server again for access to companyweb?
|
| Thanks in advance for any help or advice received.... you might just
| bail me out of the hole I find myself in! Thanks....
|
|
.
- Follow-Ups:
- RE: Cannot access companyweb
- From: chace zhang
- RE: Cannot access companyweb
- References:
- Cannot access companyweb
- From: ByrneDM
- Cannot access companyweb
- Prev by Date: Re: RDP, RWW and VPN difference
- Next by Date: Re: APC UPS shutdown and SBS
- Previous by thread: RE: Cannot access companyweb
- Next by thread: RE: Cannot access companyweb
- Index(es):
Relevant Pages
|
