Re: Connectcomputer works partly but does not complete



If you had installed updates that needed a reboot, and delayed that reboot,
that could have caused the problems.

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Rob C" <RobC@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:10F3AD98-EDEE-40F3-8483-6A7F8A1A1835@xxxxxxxxxxxxxxxx
Marina thanks for the info.

The issue has just been resolved by (wait for it) rebooting the server...
I had to due to some updates that I installed on the server, so bounced it
at lunch time. Then logged off and on the problem clients and everything
worked.
Strange eh? I wonder what that could have been?

"Marina Roos [SBS-MVP]" wrote:

Hi Rob,

The connectcomputer does create a logfile on the client. In Program
Files\Microsoft Windows Small Business Server you will find the
sbsnetstup.log file. Check that one.

--
Regards,

Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum:
http://www.smallbizserver.net/Default.aspx?tabid=53

"Rob C" <RobC@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:EB447F8A-2A80-40E4-979E-CF7FF0490428@xxxxxxxxxxxxxxxx
Hi Jason, thanks for the help.

What happens when a user assigned to the new workstation logs on to
the
system?
Still nada. Nix. The PC logs ono windows but that's about it.
I have 8 other machines all successfully connected to the domain
before
using 'connectcomputer' and then logging on as either domain admin or
the
user assigned to the PC.

Does your domain administrator account have a login script assigned
to
the
account?
No, not that I can tell. I have never assigned a script to the admin
account. I have checked default domain policy. Anywhere else I should
be
looking?

Does the client setup executable get called in the login script?
* \\SERVER\Clients\Setup\setup.exe /s SERVER
Yes. Just that one line. I do see the script being called when the
PC's
logon. you see the cmd window open minimised for a very short time.

A few months ago I did try joining a Vista PC to the domain without
much
luck. could this be related? (


http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?&query=robc+vista&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.windows.server.sbs&p=1&tid=2462d44c-7a74-4ff3-8127-0d10918a013a
) I never could get it to join via the wizard, so I had to join
manually
and
leave it at that.

Maybe I have opened a steaming cauldron of messy gook ?!




"Jason Miller [SBS-MVP]" wrote:

Hi Rob,

What happens when a user assigned to the new workstation logs on to
the

system?

Does your domain administrator account have a login script assigned
to
the
account?

Does the client setup executable get called in the login script?
* \\SERVER\Clients\Setup\setup.exe /s SERVER

Cheers,

Jason

"Rob C" <RobC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8653B4B0-30AA-48A0-B33E-548864400997@xxxxxxxxxxxxxxxx
SBS2003 SP2 Standard Exchange SP2

Hi folks.

Recently I have tried to add 2 new XP Pro SP2 computers to our
domain
and
have had the exact the same issue with both:

The connectcomputer wizard begins via
http://server/connectcomputer ,
reboots twice as it looks as though things are going well, but
when
this
completes and I log on manually (as domain admin), nothing more
has
been
applied. No SP check, no Outlook install, no IE homepage change,
no
user.lnk.
It's almost as though part of the policy does not apply.
Double checking both computers have had the client applications
re-applied
on the server, and I have logged off and back on but still
nothing.

When I check the server side, I can see the new computer is added
and
is
correctly listed with servicepack info.

Is there a log created on client or server when it is joining the
domain
that I can check?

Is this something to do with part of the group policy failing to
apply?

Any pointers as to what might be going wrong here?

Much obliged for any help you may have.






.



Relevant Pages

  • Re: Connecting a remote workstation to a domain
    ... The Server is located in DC and the CEO now lives ... remark that you will have to reboot the workstation. ... make sure you choose the SBS-domain from the drop down box, ... After the login script has finished and if you have Premium, ...
    (microsoft.public.windows.server.sbs)
  • Re: Slow opening of files
    ... You shouldn't be mapping drives on the server at all - no login script ... Also, the ipconfig /all from the server & a client, just in case. ... shows upto to 4 files and folders until the document opens ...
    (microsoft.public.windows.server.sbs)
  • Re: WINS 4204 Every 40 Minutes
    ... If the issue still exists after the server ... > there is a Windows XP client connected to the network through VPN. ... the NetBIOS name can be resolved by sending NetBIOS broadcast. ... >>of weeks so if it needs to reboot, I'll have no updates until then. ...
    (microsoft.public.windows.server.sbs)
  • Re: nfs tranfers hang in state getblck or nfsread
    ... > Reboot the client system, reboot, and remount ... > Thrash the file system a bit with large reads/writes, and it hangs ... As my server "never" shuts down and the 5-current client is switched off ... In my case there's no server reboot. ...
    (freebsd-current)
  • Re: Login Script problem
    ... > We have SBS 2000 server and I have created a login script to sync the ... > server time to all the clients system. ... What client OS? ... > as Aditional Domain Controller. ...
    (microsoft.public.backoffice.smallbiz2000)

Quantcast