Help me add a client from remote with SBS 2003

Question:

I'm remote but can log into the SBS server as administrator.

Houston is plugging in a New Workstation with Vista Business

The new client will be:

Computer Name HPF06

Full Computer name: HPF06.XXXX.local

Domain xxxx.local

If I have Houston Plug this Vista machine on. Is there a way for them to
help it see the network? AND THEN

Could someone help me go thru the steps to add it to the list and domian in
the Server so that it can be seen not only on the local domain, but by the
remote users.

I know this is alot to ask. but, I am really getting tired of dragging a guy
out at a buck fifty an hour for him to do this in 3 minutes, and charge 3
hours. I know.... don't say it.

I just need some help.

mark

Bill
Sat May 03 14:13:34 PDT 2008

Can you reach the workstation remotely?

If you have local administrator credentials on the workstation, and the
firewall has been opened for RDP and RDP has been enabled, you should be
able to do this remotely, just as if you were sitting at the machine.

"Mark" <Mark@discussions.microsoft.com> wrote in message
news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> Question:
>
>
>
> I'm remote but can log into the SBS server as administrator.
>
> Houston is plugging in a New Workstation with Vista Business
>
>
>
> The new client will be:
>
>
>
> Computer Name HPF06
>
> Full Computer name: HPF06.XXXX.local
>
> Domain xxxx.local
>
>
>
> If I have Houston Plug this Vista machine on. Is there a way for them to
> help it see the network? AND THEN
>
>
>
> Could someone help me go thru the steps to add it to the list and domian
> in
> the Server so that it can be seen not only on the local domain, but by the
> remote users.
>
>
>
> I know this is alot to ask. but, I am really getting tired of dragging a
> guy
> out at a buck fifty an hour for him to do this in 3 minutes, and charge 3
> hours. I know.... don't say it.
>
>
>
> I just need some help.
>
>
>
> mark
>

Larry
Sat May 03 14:21:34 PDT 2008

Hi Mark:

Add the patches for Vista to your SBS, and the patches for SBS to the Vista.
See Vista Notes below:

Download, install, and run the SBS BPA, and fix any issues it finds.

www.sbsbpa.com

Using the wizards, add a computer or, if a new users, add a user / computer.

you will need someone on site to do this next bit:

From the computer, open a browser and type:

http://servername/connectcomputer

and follow the bouncing ball.

Vista Notes:

Follow these links for Vista patches to apply to the SBS server:

Install the Vista and Outlook 2007 compatibility update on the SBS server
http://www.microsoft.com/downloads/details.aspx?FamilyId=9BF2F1E4-1B2C-471B-A284-E0C8C169FAC3&displaylang=en

or:

http://www.microsoft.com:80/downloads/details.aspx?FamilyID=46E95C56-1A4C-45BD-8D69-5F41FF8F1F22&displaylang=en

Be sure to read the bottom part of this page for additional requirements.

Here is another MS article about the same fix:
Windows Small Business Server 2003: Windows Vista and Outlook 2007
compatibility update
http://support.microsoft.com/?id=926505

Review the following: Each has a couple of links to follow:
http://support.microsoft.com/kb/555912

For Vista Clients to work properly with SBS 2003:
To join the domain, Vista must be Business, Enterprise or Ultimate.
And should/must be joined to the SBS network using the connectcomputer
wizard

http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-installed.aspx

There have been issues with slow logon times, where turning off auto-tuning
on the Vista client may help:
From a command prompt, type:
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled "

Also, disable all firewalls. Pay particular attention to McAffee, as you
must disable all services in MSCONFIG.

Possible DNS Config Problems

Check your DNS settings on the Vista client.

In particular if you are using "Append these DNS suffixes (in order):" make
sure the internal
domain is in the list and at the top.

At a command prompt you should be able to resolve the server name without a
DNS suffix (e.g.
nslookup servername).

WSUS 2.0?
One thread discussed a problem with an older installation of WSUS that would
not update Vista
Not tested by me.:

Old installation prior to Nov 2006 of WSUS that does not allow Vista Patches
?
1. If the WSUS was installed prior to November, you need to go back into
the WSUS console and unclick all products/save/reclick all products/save and
resync.

2. If you are behind wsus 2.0 you need to install wsus 30 to allow the Vista
to manually MU. Behind 2.0 it won't/can't.

--
Larry

Please post the resolution to
your issue so that all can benefit.

"Mark" <Mark@discussions.microsoft.com> wrote in message
news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> Question:
>
>
>
> I'm remote but can log into the SBS server as administrator.
>
> Houston is plugging in a New Workstation with Vista Business
>
>
>
> The new client will be:
>
>
>
> Computer Name HPF06
>
> Full Computer name: HPF06.XXXX.local
>
> Domain xxxx.local
>
>
>
> If I have Houston Plug this Vista machine on. Is there a way for them to
> help it see the network? AND THEN
>
>
>
> Could someone help me go thru the steps to add it to the list and domian
> in
> the Server so that it can be seen not only on the local domain, but by the
> remote users.
>
>
>
> I know this is alot to ask. but, I am really getting tired of dragging a
> guy
> out at a buck fifty an hour for him to do this in 3 minutes, and charge 3
> hours. I know.... don't say it.
>
>
>
> I just need some help.
>
>
>
> mark
>

Mark
Sat May 03 14:22:00 PDT 2008

The person plugging it in and turning it on will have no idea what he is
doing other than pushing the ON button, and placing the ethernet in.

I need abit more hlep from there to make this Client HPF06 from where I am
at .. sorry. and Thanks. Yes I have full rights as Admin.

We have a local group admin user called HPFuser01. The can log in anywhere.
But, I am the onw with Server admin rights and rights over the domain.

Can you help me help them?

"Bill Sanderson" wrote:

> Can you reach the workstation remotely?
>
> If you have local administrator credentials on the workstation, and the
> firewall has been opened for RDP and RDP has been enabled, you should be
> able to do this remotely, just as if you were sitting at the machine.
>
> "Mark" <Mark@discussions.microsoft.com> wrote in message
> news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> > Question:
> >
> >
> >
> > I'm remote but can log into the SBS server as administrator.
> >
> > Houston is plugging in a New Workstation with Vista Business
> >
> >
> >
> > The new client will be:
> >
> >
> >
> > Computer Name HPF06
> >
> > Full Computer name: HPF06.XXXX.local
> >
> > Domain xxxx.local
> >
> >
> >
> > If I have Houston Plug this Vista machine on. Is there a way for them to
> > help it see the network? AND THEN
> >
> >
> >
> > Could someone help me go thru the steps to add it to the list and domian
> > in
> > the Server so that it can be seen not only on the local domain, but by the
> > remote users.
> >
> >
> >
> > I know this is alot to ask. but, I am really getting tired of dragging a
> > guy
> > out at a buck fifty an hour for him to do this in 3 minutes, and charge 3
> > hours. I know.... don't say it.
> >
> >
> >
> > I just need some help.
> >
> >
> >
> > mark
> >
>

Mark
Sat May 03 14:26:02 PDT 2008

It hasn't been plugged in yet. And that was the basis for the question. I'd
like help being able to see it from remote... They won't know much not even
http://server/connectcomputer

we will see.

"Bill Sanderson" wrote:

> Can you reach the workstation remotely?
>
> If you have local administrator credentials on the workstation, and the
> firewall has been opened for RDP and RDP has been enabled, you should be
> able to do this remotely, just as if you were sitting at the machine.
>
> "Mark" <Mark@discussions.microsoft.com> wrote in message
> news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> > Question:
> >
> >
> >
> > I'm remote but can log into the SBS server as administrator.
> >
> > Houston is plugging in a New Workstation with Vista Business
> >
> >
> >
> > The new client will be:
> >
> >
> >
> > Computer Name HPF06
> >
> > Full Computer name: HPF06.XXXX.local
> >
> > Domain xxxx.local
> >
> >
> >
> > If I have Houston Plug this Vista machine on. Is there a way for them to
> > help it see the network? AND THEN
> >
> >
> >
> > Could someone help me go thru the steps to add it to the list and domian
> > in
> > the Server so that it can be seen not only on the local domain, but by the
> > remote users.
> >
> >
> >
> > I know this is alot to ask. but, I am really getting tired of dragging a
> > guy
> > out at a buck fifty an hour for him to do this in 3 minutes, and charge 3
> > hours. I know.... don't say it.
> >
> >
> >
> > I just need some help.
> >
> >
> >
> > mark
> >
>

Mark
Sat May 03 14:33:01 PDT 2008

That's the ticket. We already have Vista clients on the domain. I just was
concernerd about the amatuer nameing the client HPF06 and running
http://server/connectcomputer

From there your instructions are great.

Once I can see it from RD I would be fine... for the rest. It'ss getin it
there.. from here.. follow that?

If he runs: http://server/connectcomputer will it ask him for a PC name etc..

Thanks.. Thanks very much

"Larry Struckmeyer [SBS-MVP]" wrote:

> Hi Mark:
>
> Add the patches for Vista to your SBS, and the patches for SBS to the Vista.
> See Vista Notes below:
>
> Download, install, and run the SBS BPA, and fix any issues it finds.
>
> www.sbsbpa.com
>
> Using the wizards, add a computer or, if a new users, add a user / computer.
>
> you will need someone on site to do this next bit:
>
> From the computer, open a browser and type:
>
> http://servername/connectcomputer
>
> and follow the bouncing ball.
>
> Vista Notes:
>
> Follow these links for Vista patches to apply to the SBS server:
>
> Install the Vista and Outlook 2007 compatibility update on the SBS server
> http://www.microsoft.com/downloads/details.aspx?FamilyId=9BF2F1E4-1B2C-471B-A284-E0C8C169FAC3&displaylang=en
>
> or:
>
> http://www.microsoft.com:80/downloads/details.aspx?FamilyID=46E95C56-1A4C-45BD-8D69-5F41FF8F1F22&displaylang=en
>
>
> Be sure to read the bottom part of this page for additional requirements.
>
> Here is another MS article about the same fix:
> Windows Small Business Server 2003: Windows Vista and Outlook 2007
> compatibility update
> http://support.microsoft.com/?id=926505
>
> Review the following: Each has a couple of links to follow:
> http://support.microsoft.com/kb/555912
>
>
> For Vista Clients to work properly with SBS 2003:
> To join the domain, Vista must be Business, Enterprise or Ultimate.
> And should/must be joined to the SBS network using the connectcomputer
> wizard
>
> http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-installed.aspx
>
> There have been issues with slow logon times, where turning off auto-tuning
> on the Vista client may help:
> From a command prompt, type:
> netsh interface tcp set global rss=disabled
> netsh interface tcp set global autotuninglevel=disabled "
>
> Also, disable all firewalls. Pay particular attention to McAffee, as you
> must disable all services in MSCONFIG.
>
> Possible DNS Config Problems
>
> Check your DNS settings on the Vista client.
>
> In particular if you are using "Append these DNS suffixes (in order):" make
> sure the internal
> domain is in the list and at the top.
>
> At a command prompt you should be able to resolve the server name without a
> DNS suffix (e.g.
> nslookup servername).
>
>
> WSUS 2.0?
> One thread discussed a problem with an older installation of WSUS that would
> not update Vista
> Not tested by me.:
>
> Old installation prior to Nov 2006 of WSUS that does not allow Vista Patches
> ?
> 1. If the WSUS was installed prior to November, you need to go back into
> the WSUS console and unclick all products/save/reclick all products/save and
> resync.
>
> 2. If you are behind wsus 2.0 you need to install wsus 30 to allow the Vista
> to manually MU. Behind 2.0 it won't/can't.
>
> --
> Larry
>
> Please post the resolution to
> your issue so that all can benefit.
>
>
> "Mark" <Mark@discussions.microsoft.com> wrote in message
> news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> > Question:
> >
> >
> >
> > I'm remote but can log into the SBS server as administrator.
> >
> > Houston is plugging in a New Workstation with Vista Business
> >
> >
> >
> > The new client will be:
> >
> >
> >
> > Computer Name HPF06
> >
> > Full Computer name: HPF06.XXXX.local
> >
> > Domain xxxx.local
> >
> >
> >
> > If I have Houston Plug this Vista machine on. Is there a way for them to
> > help it see the network? AND THEN
> >
> >
> >
> > Could someone help me go thru the steps to add it to the list and domian
> > in
> > the Server so that it can be seen not only on the local domain, but by the
> > remote users.
> >
> >
> >
> > I know this is alot to ask. but, I am really getting tired of dragging a
> > guy
> > out at a buck fifty an hour for him to do this in 3 minutes, and charge 3
> > hours. I know.... don't say it.
> >
> >
> >
> > I just need some help.
> >
> >
> >
> > mark
> >
>
>
>

Larry
Sat May 03 14:41:34 PDT 2008

Yes, if you follow the rules, and use the wizards, it is pretty much idiot
proof.

Got to ask.... how were the rest of the computers joined to the domain, and
if you don't know, and no one there knows, then maybe you should get one of
the really good books on the subject and read up.

--
Larry

Please post the resolution to
your issue so that all can benefit.

"Mark" <Mark@discussions.microsoft.com> wrote in message
news:5965F559-9C82-466F-BB91-96FC1EDACFE5@microsoft.com...
> That's the ticket. We already have Vista clients on the domain. I just
> was
> concernerd about the amatuer nameing the client HPF06 and running
> http://server/connectcomputer
>
>
> From there your instructions are great.
>
> Once I can see it from RD I would be fine... for the rest. It'ss getin it
> there.. from here.. follow that?
>
> If he runs: http://server/connectcomputer will it ask him for a PC name
> etc..
>
> Thanks.. Thanks very much
>
>
> "Larry Struckmeyer [SBS-MVP]" wrote:
>
>> Hi Mark:
>>
>> Add the patches for Vista to your SBS, and the patches for SBS to the
>> Vista.
>> See Vista Notes below:
>>
>> Download, install, and run the SBS BPA, and fix any issues it finds.
>>
>> www.sbsbpa.com
>>
>> Using the wizards, add a computer or, if a new users, add a user /
>> computer.
>>
>> you will need someone on site to do this next bit:
>>
>> From the computer, open a browser and type:
>>
>> http://servername/connectcomputer
>>
>> and follow the bouncing ball.
>>
>> Vista Notes:
>>
>> Follow these links for Vista patches to apply to the SBS server:
>>
>> Install the Vista and Outlook 2007 compatibility update on the SBS server
>> http://www.microsoft.com/downloads/details.aspx?FamilyId=9BF2F1E4-1B2C-471B-A284-E0C8C169FAC3&displaylang=en
>>
>> or:
>>
>> http://www.microsoft.com:80/downloads/details.aspx?FamilyID=46E95C56-1A4C-45BD-8D69-5F41FF8F1F22&displaylang=en
>>
>>
>> Be sure to read the bottom part of this page for additional requirements.
>>
>> Here is another MS article about the same fix:
>> Windows Small Business Server 2003: Windows Vista and Outlook 2007
>> compatibility update
>> http://support.microsoft.com/?id=926505
>>
>> Review the following: Each has a couple of links to follow:
>> http://support.microsoft.com/kb/555912
>>
>>
>> For Vista Clients to work properly with SBS 2003:
>> To join the domain, Vista must be Business, Enterprise or Ultimate.
>> And should/must be joined to the SBS network using the connectcomputer
>> wizard
>>
>> http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-installed.aspx
>>
>> There have been issues with slow logon times, where turning off
>> auto-tuning
>> on the Vista client may help:
>> From a command prompt, type:
>> netsh interface tcp set global rss=disabled
>> netsh interface tcp set global autotuninglevel=disabled "
>>
>> Also, disable all firewalls. Pay particular attention to McAffee, as you
>> must disable all services in MSCONFIG.
>>
>> Possible DNS Config Problems
>>
>> Check your DNS settings on the Vista client.
>>
>> In particular if you are using "Append these DNS suffixes (in order):"
>> make
>> sure the internal
>> domain is in the list and at the top.
>>
>> At a command prompt you should be able to resolve the server name without
>> a
>> DNS suffix (e.g.
>> nslookup servername).
>>
>>
>> WSUS 2.0?
>> One thread discussed a problem with an older installation of WSUS that
>> would
>> not update Vista
>> Not tested by me.:
>>
>> Old installation prior to Nov 2006 of WSUS that does not allow Vista
>> Patches
>> ?
>> 1. If the WSUS was installed prior to November, you need to go back
>> into
>> the WSUS console and unclick all products/save/reclick all products/save
>> and
>> resync.
>>
>> 2. If you are behind wsus 2.0 you need to install wsus 30 to allow the
>> Vista
>> to manually MU. Behind 2.0 it won't/can't.
>>
>> --
>> Larry
>>
>> Please post the resolution to
>> your issue so that all can benefit.
>>
>>
>> "Mark" <Mark@discussions.microsoft.com> wrote in message
>> news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
>> > Question:
>> >
>> >
>> >
>> > I'm remote but can log into the SBS server as administrator.
>> >
>> > Houston is plugging in a New Workstation with Vista Business
>> >
>> >
>> >
>> > The new client will be:
>> >
>> >
>> >
>> > Computer Name HPF06
>> >
>> > Full Computer name: HPF06.XXXX.local
>> >
>> > Domain xxxx.local
>> >
>> >
>> >
>> > If I have Houston Plug this Vista machine on. Is there a way for them
>> > to
>> > help it see the network? AND THEN
>> >
>> >
>> >
>> > Could someone help me go thru the steps to add it to the list and
>> > domian
>> > in
>> > the Server so that it can be seen not only on the local domain, but by
>> > the
>> > remote users.
>> >
>> >
>> >
>> > I know this is alot to ask. but, I am really getting tired of dragging
>> > a
>> > guy
>> > out at a buck fifty an hour for him to do this in 3 minutes, and charge
>> > 3
>> > hours. I know.... don't say it.
>> >
>> >
>> >
>> > I just need some help.
>> >
>> >
>> >
>> > mark
>> >
>>
>>
>>

Mark
Sat May 03 15:00:00 PDT 2008

That is a very good question for a SBS-MVP

1. I blind interviewed companies in Houston form Daytona. I found , (I
believe an excellent Microsoft Professional company.

2. We purchased 2 Servers, (Exchange), and (a Quad Core application
Server), and we actually had an Old W2k3 Server( Now the BES Server)

3. I told them what date I needed them, I told them what the 5 clients
consisted of and the types of Servers. I told them what software we would be
running (QB Enterprise V.8.

. I told them I wanted the users local administrative rights within the
local domain clients, and not the Servers. I advised them, we had up to 4
people that would remote in. ( Not all at once!

4. I was flown into Houston by my son, the owner. And it all happened, just
as we had orchestrated it. I was very pleased. They set up the programs,
installed the Exchange Server, the Application, set up RWW, I see it all when
I log in.

I was pleased.

NOW.. Your behind the seen question. I do what I can to help them, add onto
their network ny studying very hard and reading and learning here. Sometimes
I get fantastic help and sometimes it's a chore.

I do this for my son and his partner, because it is fun, to help and learn

Now I need to add a Vista Client.. HPF06

I hate having to call in the Pro's @ $150 an hour, when I can try and learn
some of it myself. If I get stuck they get called.

Doesn't that seem fair?

mark

Thank you.. Thank you Very Much

"Larry Struckmeyer [SBS-MVP]" wrote:

> Yes, if you follow the rules, and use the wizards, it is pretty much idiot
> proof.
>
> Got to ask.... how were the rest of the computers joined to the domain, and
> if you don't know, and no one there knows, then maybe you should get one of
> the really good books on the subject and read up.
>
> --
> Larry
>
> Please post the resolution to
> your issue so that all can benefit.
>
>
> "Mark" <Mark@discussions.microsoft.com> wrote in message
> news:5965F559-9C82-466F-BB91-96FC1EDACFE5@microsoft.com...
> > That's the ticket. We already have Vista clients on the domain. I just
> > was
> > concernerd about the amatuer nameing the client HPF06 and running
> > http://server/connectcomputer
> >
> >
> > From there your instructions are great.
> >
> > Once I can see it from RD I would be fine... for the rest. It'ss getin it
> > there.. from here.. follow that?
> >
> > If he runs: http://server/connectcomputer will it ask him for a PC name
> > etc..
> >
> > Thanks.. Thanks very much
> >
> >
> > "Larry Struckmeyer [SBS-MVP]" wrote:
> >
> >> Hi Mark:
> >>
> >> Add the patches for Vista to your SBS, and the patches for SBS to the
> >> Vista.
> >> See Vista Notes below:
> >>
> >> Download, install, and run the SBS BPA, and fix any issues it finds.
> >>
> >> www.sbsbpa.com
> >>
> >> Using the wizards, add a computer or, if a new users, add a user /
> >> computer.
> >>
> >> you will need someone on site to do this next bit:
> >>
> >> From the computer, open a browser and type:
> >>
> >> http://servername/connectcomputer
> >>
> >> and follow the bouncing ball.
> >>
> >> Vista Notes:
> >>
> >> Follow these links for Vista patches to apply to the SBS server:
> >>
> >> Install the Vista and Outlook 2007 compatibility update on the SBS server
> >> http://www.microsoft.com/downloads/details.aspx?FamilyId=9BF2F1E4-1B2C-471B-A284-E0C8C169FAC3&displaylang=en
> >>
> >> or:
> >>
> >> http://www.microsoft.com:80/downloads/details.aspx?FamilyID=46E95C56-1A4C-45BD-8D69-5F41FF8F1F22&displaylang=en
> >>
> >>
> >> Be sure to read the bottom part of this page for additional requirements.
> >>
> >> Here is another MS article about the same fix:
> >> Windows Small Business Server 2003: Windows Vista and Outlook 2007
> >> compatibility update
> >> http://support.microsoft.com/?id=926505
> >>
> >> Review the following: Each has a couple of links to follow:
> >> http://support.microsoft.com/kb/555912
> >>
> >>
> >> For Vista Clients to work properly with SBS 2003:
> >> To join the domain, Vista must be Business, Enterprise or Ultimate.
> >> And should/must be joined to the SBS network using the connectcomputer
> >> wizard
> >>
> >> http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-installed.aspx
> >>
> >> There have been issues with slow logon times, where turning off
> >> auto-tuning
> >> on the Vista client may help:
> >> From a command prompt, type:
> >> netsh interface tcp set global rss=disabled
> >> netsh interface tcp set global autotuninglevel=disabled "
> >>
> >> Also, disable all firewalls. Pay particular attention to McAffee, as you
> >> must disable all services in MSCONFIG.
> >>
> >> Possible DNS Config Problems
> >>
> >> Check your DNS settings on the Vista client.
> >>
> >> In particular if you are using "Append these DNS suffixes (in order):"
> >> make
> >> sure the internal
> >> domain is in the list and at the top.
> >>
> >> At a command prompt you should be able to resolve the server name without
> >> a
> >> DNS suffix (e.g.
> >> nslookup servername).
> >>
> >>
> >> WSUS 2.0?
> >> One thread discussed a problem with an older installation of WSUS that
> >> would
> >> not update Vista
> >> Not tested by me.:
> >>
> >> Old installation prior to Nov 2006 of WSUS that does not allow Vista
> >> Patches
> >> ?
> >> 1. If the WSUS was installed prior to November, you need to go back
> >> into
> >> the WSUS console and unclick all products/save/reclick all products/save
> >> and
> >> resync.
> >>
> >> 2. If you are behind wsus 2.0 you need to install wsus 30 to allow the
> >> Vista
> >> to manually MU. Behind 2.0 it won't/can't.
> >>
> >> --
> >> Larry
> >>
> >> Please post the resolution to
> >> your issue so that all can benefit.
> >>
> >>
> >> "Mark" <Mark@discussions.microsoft.com> wrote in message
> >> news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> >> > Question:
> >> >
> >> >
> >> >
> >> > I'm remote but can log into the SBS server as administrator.
> >> >
> >> > Houston is plugging in a New Workstation with Vista Business
> >> >
> >> >
> >> >
> >> > The new client will be:
> >> >
> >> >
> >> >
> >> > Computer Name HPF06
> >> >
> >> > Full Computer name: HPF06.XXXX.local
> >> >
> >> > Domain xxxx.local
> >> >
> >> >
> >> >
> >> > If I have Houston Plug this Vista machine on. Is there a way for them
> >> > to
> >> > help it see the network? AND THEN
> >> >
> >> >
> >> >
> >> > Could someone help me go thru the steps to add it to the list and
> >> > domian
> >> > in
> >> > the Server so that it can be seen not only on the local domain, but by
> >> > the
> >> > remote users.
> >> >
> >> >
> >> >
> >> > I know this is alot to ask. but, I am really getting tired of dragging
> >> > a
> >> > guy
> >> > out at a buck fifty an hour for him to do this in 3 minutes, and charge
> >> > 3
> >> > hours. I know.... don't say it.
> >> >
> >> >
> >> >
> >> > I just need some help.
> >> >
> >> >
> >> >
> >> > mark
> >> >
> >>
> >>
> >>
>
>
>

Cris
Sat May 03 18:44:06 PDT 2008

This is a multi-part message in MIME format.

------=_NextPart_000_0063_01C8AD5E.6E4BEDA0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

When you are the person primarily responsible for a network that =
involves SBS, this is by all means the place to try and get questions =
answered.
This is a peer-to-peer support mechanism where people who volunteer =
their time try to assist folks like you.

But Larry's questions certainly are valid. It can be tough enough for =
a person who is an experienced SBS implementer to provide remote =
support.
But much, much tougher in the long term to do that support when you =
don't have first hand knowledge of the network and little to no =
experience with SBS.

You are not going to get remote access to this machine (Vista or XP) via =
RDP or RWW until it's joined to the domain, using the steps that Larry =
provided.

If you don't feel comfortable walking the onsite person through this, =
then I don't think you have much choice but to call in the support =
company.=20

--=20
Cris Hanna [SBS-MVP]
------------------------------------------
MVPs Do Not Work For Microsoft
-----------------------------------------------------
Please do not contact me directly. Please post only in the newsgroup so =
all can benefit

"Mark" <Mark@discussions.microsoft.com> wrote in message =
news:2D2F7B3A-6228-4E6F-A771-90C1F2C568EE@microsoft.com...
That is a very good question for a SBS-MVP

1. I blind interviewed companies in Houston form Daytona. I found , (I=20
believe an excellent Microsoft Professional company.

2. We purchased 2 Servers, (Exchange), and (a Quad Core application=20
Server), and we actually had an Old W2k3 Server( Now the BES Server)

3. I told them what date I needed them, I told them what the 5 clients=20
consisted of and the types of Servers. I told them what software we =
would be=20
running (QB Enterprise V.8.=20

. I told them I wanted the users local administrative rights within the=20
local domain clients, and not the Servers. I advised them, we had up to =
4=20
people that would remote in. ( Not all at once!

4. I was flown into Houston by my son, the owner. And it all happened, =
just=20
as we had orchestrated it. I was very pleased. They set up the programs, =

installed the Exchange Server, the Application, set up RWW, I see it all =
when=20
I log in.

I was pleased.

NOW.. Your behind the seen question. I do what I can to help them, add =
onto=20
their network ny studying very hard and reading and learning here. =
Sometimes=20
I get fantastic help and sometimes it's a chore.

I do this for my son and his partner, because it is fun, to help and =
learn

Now I need to add a Vista Client.. HPF06

I hate having to call in the Pro's @ $150 an hour, when I can try and =
learn=20
some of it myself. If I get stuck they get called.

Doesn't that seem fair?

mark

Thank you.. Thank you Very Much

"Larry Struckmeyer [SBS-MVP]" wrote:

> Yes, if you follow the rules, and use the wizards, it is pretty much =
idiot=20
> proof.
>=20
> Got to ask.... how were the rest of the computers joined to the =
domain, and=20
> if you don't know, and no one there knows, then maybe you should get =
one of=20
> the really good books on the subject and read up.
>=20
> --=20
> Larry
>=20
> Please post the resolution to
> your issue so that all can benefit.
>=20
>=20
> "Mark" <Mark@discussions.microsoft.com> wrote in message=20
> news:5965F559-9C82-466F-BB91-96FC1EDACFE5@microsoft.com...
> > That's the ticket. We already have Vista clients on the domain. I =
just=20
> > was
> > concernerd about the amatuer nameing the client HPF06 and running
> > http://server/connectcomputer
> >
> >
> > From there your instructions are great.
> >
> > Once I can see it from RD I would be fine... for the rest. It'ss =
getin it
> > there.. from here.. follow that?
> >
> > If he runs: http://server/connectcomputer will it ask him for a PC =
name=20
> > etc..
> >
> > Thanks.. Thanks very much
> >
> >
> > "Larry Struckmeyer [SBS-MVP]" wrote:
> >
> >> Hi Mark:
> >>
> >> Add the patches for Vista to your SBS, and the patches for SBS to =
the=20
> >> Vista.
> >> See Vista Notes below:
> >>
> >> Download, install, and run the SBS BPA, and fix any issues it =
finds.
> >>
> >> www.sbsbpa.com
> >>
> >> Using the wizards, add a computer or, if a new users, add a user /=20
> >> computer.
> >>
> >> you will need someone on site to do this next bit:
> >>
> >> From the computer, open a browser and type:
> >>
> >> http://servername/connectcomputer
> >>
> >> and follow the bouncing ball.
> >>
> >> Vista Notes:
> >>
> >> Follow these links for Vista patches to apply to the SBS server:
> >>
> >> Install the Vista and Outlook 2007 compatibility update on the SBS =
server
> >> =
http://www.microsoft.com/downloads/details.aspx?FamilyId=3D9BF2F1E4-1B2C-=
471B-A284-E0C8C169FAC3&displaylang=3Den
> >>
> >> or:
> >>
> >> =
http://www.microsoft.com:80/downloads/details.aspx?FamilyID=3D46E95C56-1A=
4C-45BD-8D69-5F41FF8F1F22&displaylang=3Den
> >>
> >>
> >> Be sure to read the bottom part of this page for additional =
requirements.
> >>
> >> Here is another MS article about the same fix:
> >> Windows Small Business Server 2003: Windows Vista and Outlook 2007
> >> compatibility update
> >> http://support.microsoft.com/?id=3D926505
> >>
> >> Review the following: Each has a couple of links to follow:
> >> http://support.microsoft.com/kb/555912
> >>
> >>
> >> For Vista Clients to work properly with SBS 2003:
> >> To join the domain, Vista must be Business, Enterprise or Ultimate.
> >> And should/must be joined to the SBS network using the =
connectcomputer
> >> wizard
> >>
> >> =
http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-i=
nstalled.aspx
> >>
> >> There have been issues with slow logon times, where turning off=20
> >> auto-tuning
> >> on the Vista client may help:
> >> From a command prompt, type:
> >> netsh interface tcp set global rss=3Ddisabled
> >> netsh interface tcp set global autotuninglevel=3Ddisabled "
> >>
> >> Also, disable all firewalls. Pay particular attention to McAffee, =
as you
> >> must disable all services in MSCONFIG.
> >>
> >> Possible DNS Config Problems
> >>
> >> Check your DNS settings on the Vista client.
> >>
> >> In particular if you are using "Append these DNS suffixes (in =
order):"=20
> >> make
> >> sure the internal
> >> domain is in the list and at the top.
> >>
> >> At a command prompt you should be able to resolve the server name =
without=20
> >> a
> >> DNS suffix (e.g.
> >> nslookup servername).
> >>
> >>
> >> WSUS 2.0?
> >> One thread discussed a problem with an older installation of WSUS =
that=20
> >> would
> >> not update Vista
> >> Not tested by me.:
> >>
> >> Old installation prior to Nov 2006 of WSUS that does not allow =
Vista=20
> >> Patches
> >> ?
> >> 1. If the WSUS was installed prior to November, you need to go =
back=20
> >> into
> >> the WSUS console and unclick all products/save/reclick all =
products/save=20
> >> and
> >> resync.
> >>
> >> 2. If you are behind wsus 2.0 you need to install wsus 30 to allow =
the=20
> >> Vista
> >> to manually MU. Behind 2.0 it won't/can't.
> >>
> >> --=20
> >> Larry
> >>
> >> Please post the resolution to
> >> your issue so that all can benefit.
> >>
> >>
> >> "Mark" <Mark@discussions.microsoft.com> wrote in message
> >> news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com...
> >> > Question:
> >> >
> >> >
> >> >
> >> > I'm remote but can log into the SBS server as administrator.
> >> >
> >> > Houston is plugging in a New Workstation with Vista Business
> >> >
> >> >
> >> >
> >> > The new client will be:
> >> >
> >> >
> >> >
> >> > Computer Name HPF06
> >> >
> >> > Full Computer name: HPF06.XXXX.local
> >> >
> >> > Domain xxxx.local
> >> >
> >> >
> >> >
> >> > If I have Houston Plug this Vista machine on. Is there a way for =
them=20
> >> > to
> >> > help it see the network? AND THEN
> >> >
> >> >
> >> >
> >> > Could someone help me go thru the steps to add it to the list and =

> >> > domian
> >> > in
> >> > the Server so that it can be seen not only on the local domain, =
but by=20
> >> > the
> >> > remote users.
> >> >
> >> >
> >> >
> >> > I know this is alot to ask. but, I am really getting tired of =
dragging=20
> >> > a
> >> > guy
> >> > out at a buck fifty an hour for him to do this in 3 minutes, and =
charge=20
> >> > 3
> >> > hours. I know.... don't say it.
> >> >
> >> >
> >> >
> >> > I just need some help.
> >> >
> >> >
> >> >
> >> > mark
> >> >
> >>
> >>
> >>=20
>=20
>=20
>
------=_NextPart_000_0063_01C8AD5E.6E4BEDA0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2900.5512" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>When you are the person primarily =
responsible for a=20
network that involves SBS, this is by all means the place to try and get =

questions answered.</DIV>
<DIV>This is a peer-to-peer support =
mechanism where=20
people who volunteer their time try to assist folks like =
you.</DIV>
<DIV> </DIV>
<DIV>But Larry's questions certainly are=20
valid.   It can be tough enough for a person who is an =
experienced SBS=20
implementer to provide remote support.</DIV>
<DIV>But much, much tougher in the long term =
to do that=20
support when you don't have first hand knowledge of the network and =
little to no=20
experience with SBS.</DIV>
<DIV> </DIV>
<DIV>You are not going to get remote access =
to=20
this machine (Vista or XP) via RDP or RWW until it's joined =
to the=20
domain, using the steps that Larry provided.</DIV>
<DIV> </DIV>
<DIV>If you don't feel comfortable walking =
the onsite=20
person through this, then I don't think you have much choice but to =
call in=20
the support company. </DIV>
<DIV> -- Cris Hanna=20
[SBS-MVP] ------------------------------------------ MVPs Do Not =
Work For=20
Microsoft ----------------------------------------------------- Ple=
ase do=20
not contact me directly.  Please post only in the newsgroup so all =
can=20
benefit</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>"Mark" <<A=20
href=3D"mailto:Mark@discussions.microsoft.com">Mark@discussions.microsoft=
.com</A>>=20
wrote in message <A=20
href=3D"news:2D2F7B3A-6228-4E6F-A771-90C1F2C568EE@microsoft.com">news:2D2=
F7B3A-6228-4E6F-A771-90C1F2C568EE@microsoft.com</A>...</DIV>That=20
is a very good question for a SBS-MVP 1. I blind interviewed =
companies in=20
Houston form Daytona. I found , (I believe an excellent Microsoft=20
Professional company. 2. We purchased 2 Servers, (Exchange), =
and  (a=20
Quad Core application Server), and we actually had an Old W2k3 =
Server( Now=20
the BES Server) 3. I told them what date I needed them, I told =
them what=20
the 5 clients consisted of and the types of Servers. I told them =
what=20
software we would be running (QB Enterprise V.8. . I told =
them I=20
wanted the users local administrative rights within the local domain =

clients,  and not the Servers. I advised them, we had up to 4 =
 people=20
that would remote in. ( Not all at once! 4. I was  flown =
into=20
Houston by my son, the owner. And it all happened, just as we had=20
orchestrated it. I was very pleased. They set up the programs, =
 installed the=20
Exchange Server, the Application, set up RWW, I see it all when I =
log=20
in. I was pleased. NOW.. Your behind the seen question. I =
do what=20
I can to help them, add onto their network ny studying very hard and =
reading=20
and learning here. Sometimes I get fantastic help and sometimes it's =
a=20
chore. I do this for my son and his partner, because it is fun, =
to help=20
and learn Now I need to add a Vista Client.. HPF06 I hate =
having=20
to call in the Pro's @ $150 an hour, when I can try and learn some =
of it=20
myself. If I get stuck they get called. Doesn't that seem=20
fair? mark Thank you.. Thank you Very Much "Larry=20
Struckmeyer [SBS-MVP]" wrote: > Yes, if you follow the rules, =
and use=20
the wizards, it is pretty much idiot > proof. > > =
Got to=20
ask.... how were the rest of the computers joined to the domain, and =
 > if=20
you don't know, and no one there knows, then maybe you should get one of =

 > the really good books on the subject and read up. > =
 > --=20
 > Larry > > Please post the resolution to > =
your issue=20
so that all can benefit. > > > "Mark" <<A=20
href=3D"mailto:Mark@discussions.microsoft.com">Mark@discussions.microsoft=
.com</A>>=20
wrote in message > <A=20
href=3D"news:5965F559-9C82-466F-BB91-96FC1EDACFE5@microsoft.com">news:596=
5F559-9C82-466F-BB91-96FC1EDACFE5@microsoft.com</A>... >=20
> That's the ticket.   We already have Vista clients on the =
domain.=20
I just > > was > > concernerd about the amatuer =
nameing the=20
client HPF06 and running > > <A=20
href=3D"http://server/connectcomputer">http://server/connectcomputer</A><=
BR>>=20
> > > > > From there your instructions are =
great. >=20
> > > Once I can see it from RD I would be fine... for the =
rest.=20
It'ss getin it > > there.. from here.. follow that? >=20
> > > If he runs: <A=20
href=3D"http://server/connectcomputer">http://server/connectcomputer</A> =
will it=20
ask him for a PC name > > etc.. > > > > =
Thanks..=20
Thanks very much > > > > > > "Larry =
Struckmeyer=20
[SBS-MVP]" wrote: > > > >> Hi Mark: >=20
>> > >> Add the patches for Vista to your SBS, and the =
patches=20
for SBS to the > >> Vista. > >> See Vista Notes =

below: > >> > >> Download, install, and run the =
SBS BPA,=20
and fix any issues it finds. > >> > >> <A=20
href=3D"http://www.sbsbpa.com">www.sbsbpa.com</A> > =
>> >=20
>> Using the wizards, add a computer or, if a new users, add a =
user /=20
 > >> computer. > >> > >> you will =
need=20
someone on site to do this next bit: > >> > >> =
From the=20
computer, open a browser and type: > >> > >> <A=20
href=3D"http://servername/connectcomputer">http://servername/connectcompu=
ter</A> >=20
>> > >> and follow the bouncing ball. > =
>> >=20
>> Vista Notes: > >> > >> Follow these =
links for=20
Vista patches to apply to the SBS server: > >> > =
>>=20
Install the Vista and Outlook 2007 compatibility update on the SBS=20
server > >> <A=20
href=3D"http://www.microsoft.com/downloads/details.aspx?FamilyId=3D9BF2F1=
E4-1B2C-471B-A284-E0C8C169FAC3&displaylang=3Den">http://www.microsoft=
.com/downloads/details.aspx?FamilyId=3D9BF2F1E4-1B2C-471B-A284-E0C8C169FA=
C3&displaylang=3Den</A> >=20
>> > >> or: > >> > >> <A=20
href=3D"http://www.microsoft.com:80/downloads/details.aspx?FamilyID=3D46E=
95C56-1A4C-45BD-8D69-5F41FF8F1F22&displaylang=3Den">http://www.micros=
oft.com:80/downloads/details.aspx?FamilyID=3D46E95C56-1A4C-45BD-8D69-5F41=
FF8F1F22&displaylang=3Den</A> >=20
>> > >> > >> Be sure to read the bottom =
part of=20
this page for additional requirements. > >> > >> =
Here is=20
another MS article about the same fix: > >> Windows Small =
Business=20
Server 2003: Windows Vista and Outlook 2007 > >> =
compatibility=20
update > >> <A=20
href=3D"http://support.microsoft.com/?id=3D926505">http://support.microso=
ft.com/?id=3D926505</A> >=20
>> > >> Review the following: Each has a couple of =
links to=20
follow: > >> <A=20
href=3D"http://support.microsoft.com/kb/555912">http://support.microsoft.=
com/kb/555912</A> >=20
>> > >> > >> For Vista Clients to work =
properly=20
with SBS 2003: > >> To join the domain, Vista must be =
Business,=20
Enterprise or Ultimate. > >> And should/must be joined to =
the SBS=20
network using the connectcomputer > >> wizard >=20
>> > >> <A=20
href=3D"http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-aft=
er-sp2-installed.aspx">http://msmvps.com/blogs/bradley/archive/2007/04/04=
/vista-slow-after-sp2-installed.aspx</A> >=20
>> > >> There have been issues with slow logon times, =
where=20
turning off > >> auto-tuning > >> on the Vista =
client=20
may help: > >> From a command prompt, type: > >> =
netsh=20
interface tcp set global rss=3Ddisabled > >> netsh interface =
tcp set=20
global autotuninglevel=3Ddisabled " > >> > >> =
Also,=20
disable all firewalls.  Pay particular attention to McAffee, as =
you >=20
>> must disable all services in MSCONFIG. > >> > =

>> Possible DNS Config Problems > >> > >> =
Check=20
your DNS settings on the Vista client. > >> > >> =
In=20
particular if you are using "Append these DNS suffixes (in order):" =
 >=20
>> make > >> sure the internal > >> domain =
is in=20
the list and at the top. > >> > >> At a command =
prompt=20
you should be able to resolve the server name without > >>=20
a > >> DNS suffix (e.g. > >> nslookup=20
servername). > >> > >> > >> WSUS=20
2.0? > >> One thread discussed a problem with an older =
installation=20
of WSUS that > >> would > >> not update =
Vista >=20
>> Not tested by me.: > >> > >> Old =
installation=20
prior to Nov 2006 of WSUS that does not allow Vista > >>=20
Patches > >> ? > >>     1. =
If the=20
WSUS was installed prior to November, you need to go back > =
>>=20
into > >> the WSUS console and unclick all =
products/save/reclick all=20
products/save > >> and > >> resync. >=20
>> > >> 2. If you are behind wsus 2.0 you need to =
install wsus=20
30 to allow the > >> Vista > >> to manually MU. =
Behind=20
2.0 it won't/can't. > >> > >> -- > =
>>=20
Larry > >> > >> Please post the resolution =
to >=20
>> your issue so that all can benefit. > >> >=20
>> > >> "Mark" <<A=20
href=3D"mailto:Mark@discussions.microsoft.com">Mark@discussions.microsoft=
.com</A>>=20
wrote in message > >> <A=20
href=3D"news:67FE8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com">news:67F=
E8E54-BAE7-4D3B-B742-5722BA8D1BB7@microsoft.com</A>... >=20
>> > Question: > >> > > >> =
> >=20
>> > > >> > I'm remote but can log into the SBS =
server=20
as administrator. > >> > > >> > Houston is =

plugging in a New Workstation with Vista Business > >> =
> >=20
>> > > >> > > >> > The new client =
will=20
be: > >> > > >> > > >> =
> >=20
>> > Computer Name HPF06 > >> > > >> =
>=20
Full Computer name: HPF06.XXXX.local > >> > > =
>> >=20
Domain xxxx.local > >> > > >> > > =
>>=20
> > >> > If I have Houston Plug this Vista machine on. =
Is=20
there a way for them > >> > to > >> > =
help it see=20
the network? AND THEN > >> > > >> =
> >=20
>> > > >> > Could someone help me go thru the =
steps to=20
add it to the list and > >> > domian > >> =
>=20
in > >> > the Server so that it can be seen not only on =
the local=20
domain, but by > >> > the > >> > remote=20
users. > >> > > >> > > >> =
> >=20
>> > I know this is alot to ask. but, I am really getting tired =
of=20
dragging > >> > a > >> > guy > =
>>=20
> out at a buck fifty an hour for him to do this in 3 minutes, and =
charge=20
 > >> > 3 > >> > hours.  I know.... =
don't say=20
it. > >> > > >> > > >> =
> >=20
>> > I just need some help. > >> > > =
>>=20
> > >> > > >> > mark > >>=20
> > >> > >> > >> > =
 >=20
 ></BODY></HTML>

------=_NextPart_000_0063_01C8AD5E.6E4BEDA0--

Help me add a client from remote with SBS 2003

Re: Help me add a client from remote with SBS 2003 by Bill

Re: Help me add a client from remote with SBS 2003 by Larry

Re: Help me add a client from remote with SBS 2003 by Mark

Re: Help me add a client from remote with SBS 2003 by Mark

Re: Help me add a client from remote with SBS 2003 by Mark

Re: Help me add a client from remote with SBS 2003 by Larry

Re: Help me add a client from remote with SBS 2003 by Mark

Re: Help me add a client from remote with SBS 2003 by Cris