Re: where is the outlook 2003 product key on the SBS2003 R2 DVD

One thing that DHCP on SB Scan do that most routers cannot is to force
dynamic updates and create PTR records in DNS. That helps with domain
communication. Assigning reservations is also easier and a lot of the
tracking is easier from the server.

All you need to do is make sure there are no other DHCP servers running on
the LAN side of your SBS network (usually a router's DHCP).

The only time I have seen the connectcomputer error you mentioned about DNS
is when the ISP DNS is set on the clients instead of the SBS DNS IP address.

Gregg Hill


"Jim Evans" <JimEvans@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:51BD6F2D-BE68-4DA7-B133-93EFB57E90BF@xxxxxxxxxxxxxxxx
I would rather setup a real server with a real client PC and a real router
at
my work network and see what the results are first. One thing I have done
with all of the networks I support is to let the router take care of DHCP.
The first version of SBS2003 and the sp1 version always whined about an
external DHCP server. I don't install dhcp on the servers, because i
don't
quite know how to "authorize" external dhcp servers. I do know to set the
clients dns to point to the servers dns and set up dns forwarding on the
server to point to ISP's DNS.

Having said all of that, I'm sure that it is probably preferred to let the
SBS do DNS and DHCP. I just don't want to change all of the networks
over.

This virtual project was to become familiar with the wizards and is hardly
a
"real world scenario" resulting in "real world" results.

"Gregg Hill" wrote:

If you had your DNS and DHCP set up properly on the server, you would not
be
getting that error message.

Post an "ipconfig /all" from your server and a workstation and I can tell
if
you have it set up correctly.

Gregg Hill




"Jim Evans" <JimEvans@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C27A101D-B177-4D64-B032-1E453A526D7C@xxxxxxxxxxxxxxxx
Okay thanks for all of the input....

I did make alot of progress. However, I couldn't get the client to
connect
to the server through the "http://sbs/connectcomputer"; method. I did,
however get connected to the DC through the network setup wizard on the
client. When it logged onto the domain, the client had an icon to
"install
outlook". When I clicked on it, it came up with the product key
window.
What did I do wrong?

A little background is this...

I'm using virtual pc 2007 for both the server and the client. for the
first
time EVER, I got the internet to work on the server with 2 NIC's after
running CEICW. I added the client PC and the user using the wizards.
when I
did this... http://sbs/connectcomputer , i got an error something to
the
effect of set DNS in the router to the ip of the server, so I chose to
join
the domain using the clients network wizard. This is just a lab setup
and
I
don't want to change router to do DNS at this point. I'm just trying
to
get
through all of these wizards and get a feel for what a SBS2003 properly
installed is like.

I am very inpressed that when the clients connect, software can be
installed
automatically. I didn't know that.

My main push is I have one of these boxes going into a 15 client
network
next week and would like to impress my customer. I've installed 3
other
SBS
servers this year and the results were lame. He now has a XP peer
network
and has finally opted to get a server. I also have a service contract
with
our local county and one of my goals in 2007 is to get the 70-282
certificate. the training is led by microsoft and is on jan 12. I'm
trying
over this christmas break to get a better foundation on this.

As others has often said, I don't have any problems installing and
configuring server 2003, just these SBS servers.

Thanks again for all of the input.

""Inn Jin [MSFT]"" wrote:

Hi Jim.

Thank you for posting here.

From the description, I understand you want to install only outlook
2003
SP2 on your computer and want to know where the product key is on your
SBS2003 R2 DVD. If I am off base, please don't hesitate to let me
know.

Base on my knowledge, the only way to install Outlook 2003 SP2 on a
single
computer from SBS 2003 R2 DVD is through deployment of the SBS server.
I
completed understand your situation, but windows SBS 2003 R2 is
designed
for a business solution, not for personal need. The goal of design is
provide a convenient way for a business environment. We don't have a
method
to install Outlook 2003 SP2 in a separate computer without any Server
involved, so we don¡¯t provide Outlook 2003 product key on the DVD.

I appreciate your understanding, I am happy to be of assistance to you
and
look forward to your reply.

Have a nice day!

Best regards,

Inn Jin (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.







.

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • RE: RPC Service unavailable
    ... Below are settings with fixed and DHCP settings on one op the clients: ... DNS Suffix search list: maddogs.local ... also when setting things on DHCP I can still access the client woth RDP ... is that the dhcp server is assigning some options incorrectly, ...
    (microsoft.public.windows.server.dns)
  • Re: RRAS and FQDN (connection-specific dns suffix is blank)
    ... domain within the DNS tab of TCP/IP properties so that names are resolved properly but this doesn't solve the issue with the server not being able to hand out the domain suffix to the vpn client when the clien logs in. ... this would be done via DHCP but I'm using a static set of IP addresses for vpn clients. ... The client does not get its network config directly from DHCP even if you use the DHCP option. ...
    (microsoft.public.windows.server.networking)
  • Re: Application Hang
    ... If the workstation ip is expired, the lease time is exceeded, delete the ip on the DHCP server "address leases" and run ipconfig /renew on the workstation. ... The forwarders ip is only used form the DNS server, all domain members will ask the domain DNS server for the www.whatever.com address, if the server doesn't know it, it will automatically forward ther request to the ip addresses under the forwarders tab. ... When I do a "ipconfig /all" on the client, ...
    (microsoft.public.windows.server.networking)
  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)