Re: Client connect with SBS 2003

OK - thanks. So for now I can see the server, transfer files etc but really I
want to upgrade to XP Pro. Cheers.

(Love the name btw)

"Lanwench [MVP - Exchange]" wrote:

Mick Jennings <MickJennings@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks. I added the appropriate IP to the "Intranet" zone and set the
security to low, the it ran.

Unfortunately it then told me I am running Windows XP Home Edition on
this machine (bugger - forgot that). Can XP Home be configured to
work with SBS 2003, Exchange, etc (after all, it is communicating
now)

It can "communicate" - meaning, you can access resources in the domain, if
you provide valid domain credentials - but you cannot *join* the domain.
This is really no different from Win9x computers; they can open files,
access Exchange, whatnot, but they cannot join a domain. Oh, and WinXP Media
Center Edition can't do that either.

You really want all clients to be running XP Pro. You lose out on a lot of
things if you don't join all workstationsto the domain.

or do I need to upgrade to Business ?

You mean "Pro" ...unless you're talking about Vista, which I think is best
avoided for now anyway.


Is it simply a case of
manually configuring the network and Exchange ?

"fast247.biz" wrote:

First question: you can disable 2003 client install on the server for
each user if you're going to install office 2007
Second question: make sure your pref & security settings in browser
are set to default & your firewall isn;t blocking communication. Then
try again



On 2 May, 15:56, Mick Jennings
<MickJenni...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi all - first time installer here. I have SBS 2003 R2 up and
running with internal and external NICs set up and working. I've
added myself as a user, time to connect my PC.

First question. My PC already has Office 2007 installed along with
Outlook 2007 and Business Contact Manager. I've backed it all up,
but I'd rather not mess it up and have to restore. During the user
setup on the server I am prompted to install 4 items to the client
(client os service packs, IE 6, Outlook 2003, Shared Fax Client).
I'm tempted to only check the last of these as I'm already way moee
up to date. Will I lose out on the server configuring the more up
to date items for me (for example Outlook 2007 connecting to
Exchange) ? Should I check all items and hope it's clever enough
not to install an older component ?

Second question. Browsing to 192.168.16.2 (internal NIC) brings up
the "Welcome to Windows SBS" page with 4 options (Company Web,
Network Config Wizard, RWW, Info & Help) so I know I can connect
ok. If I choose the Network Config Wizard it asks me to install an
ActiveX control which I did. It then just stops at a page saying
"Run the wizard to complete networking setup". I've tried going
back and firth over this step but it always stops at this point.
Any clues ?




.

Relevant Pages

  • Re: Client connect with SBS 2003
    ... You really want all clients to be running XP Pro. ... setup on the server I am prompted to install 4 items to the client ... (client os service packs, IE 6, Outlook 2003, Shared Fax Client). ... Network Config Wizard, RWW, Info & Help) so I know I can connect ...
    (microsoft.public.windows.server.sbs)
  • Re: Changing OS on Dual Boot PC
    ... | I want to now put an instance of XP Pro on my drive C. ... | Do I need to "fix" the dual boot configuration after I install XP Pro? ...
    (microsoft.public.win2000.general)
  • Re: testing ASP pages with Windows Front Page
    ... justification for XP Pro. ... > server-side scripting, such as ASP, ASP.net, PHP, etc. ... >> had to install Personal Web Server to it in order to do the job. ...
    (microsoft.public.frontpage.addins)
  • Re: xp or professional
    ... If you want to experiment and learn about things like Web Servers then Pro is by far the best choice since it can do most things that the proprietary server software can do. ... Server versions install more and have more on by default, so there's less for an IT Pro to configure.Home takes this a stage further by losing the ability to install such things as web or mail servers, Pro can do that but it is optional, Server systems generally do install that kind of stuff because it's assumed that if you didn't want it you wouldn't be buying the server product. ...
    (microsoft.public.windowsxp.general)
  • Re: testing ASP pages with Windows Front Page
    ... You can upgrade from Home to Pro. ... >> Thomas A. Rowe (Microsoft MVP - FrontPage) ... >>> Personal Web Server to it in order to do the job. ... >>> install a server on my XP just to test ASP pages. ...
    (microsoft.public.frontpage.addins)