Re: ADVANCED CLIENT INSTALLED BUT...

Dave,

This is one of the longest running threads by one person :)

Midway through your posts, I noticed the overlapping i/o error. I'm certain
that there was a hotfix for that... In searching the knowledge base, I did
find this one:

http://support.microsoft.com/kb/899362/en-us

but I think more likely it's this:
http://support.microsoft.com/kb/906570/en-us

As a sanity check, run the management point troubleshooting utility (sms
toolkit 2) from one of your clients.

Steve

"Mr Durand" <eldocomp@xxxxxxxxx> wrote in message
news:u5lYxutUGHA.5884@xxxxxxxxxxxxxxxxxxxxxxx
OK....waiting nearly 24 hours for a machine to show as "installed" is
unacceptable. I recall in previous versions of SMS you could "turn-up"
the processing of the site tasks and I believe the fastest may have been
called "TEST" mode. In version 1.2 I ran my site in test mode all the
time and had no problems. Is there anyway in SMS 2003 to adjust an
equivalent setting?

MrDurand



"Mr Durand" <eldocomp@xxxxxxxxx> wrote in message
news:uxYUgFqUGHA.4864@xxxxxxxxxxxxxxxxxxxxxxx
looks like a flaw somewhere....my site server runs Windows 2000 SP4 and
my MP runs Windows 2003 SP1. To get this error message to vanish, I had
to give 'Everyone' permissions to numerous registry hives on the site
server under HKLM\Software\Microsoft\SMS so now the error messages are no
longer appearing in that log and the other logs on the management point
indicate all systems are started and running without errors however I
still do not have client data in the database nor do any of the clients
indicate they are installed as far as the database goes though the client
components appear to be installed on the workstations as I had directed
as verified via the install logs on the client and the settings present
in the control panel applet.


Mr Durand




"Mr Durand" <eldocomp@xxxxxxxxx> wrote in message
news:e3LEuipUGHA.2704@xxxxxxxxxxxxxxxxxxxxxxx
I'm seeing a variety of errors on the management point however the one
that clearly must be an issue is as follows from the SMSEXEC.LOG file on
the Management Point (a different server than the site server itself).
The MP server is in the local Administrators group of the SMS Site
Server. Both machines have been restarted and the issue is still
occuring.

ERROR: Could not connect to registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\SMS on site server SMSSITESERVER,
sleeping 60 seconds. The operating system reported error 997:
Overlapped I/O operation is in progress.


"Mr Durand" <eldocomp@xxxxxxxxx> wrote in message
news:Oza7VLoUGHA.776@xxxxxxxxxxxxxxxxxxxxxxx
I fell victim to the SMSClient share not being created on my Management
Point so after creating manually my client appeared to have installed
error free (at least the logs are happy) however the information is not
making it's way to the database to show the client is installed and
aware of inventories, etc.

I can't find any errors in the CcmExec.log file and when using the
MPSpy and MPTroubleshooter tools from the client they seem to
communicate perfectly with the MP.

What am I missing? I can't find errors in my logs and my MP and CAPs
look like ghost towns. I've been pretty saavy at SMS in the past but
the advanced client definitely poses new challenges.

MrDurand (a.k.a. Dave)









.

Relevant Pages

  • Re: Fax on Terminal Server from SBS2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... 248340 Installing and Using Programs in Windows 2000 Terminal Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... The SBS server is running SP2. ... However I don't know if the client computers do. ... To successfully install SBS 2003 SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Fax on Terminal Server from SBS2K3
    ... activity logging in the shared fax in the server box. ... Microsoft CSS Online Newsgroup Support ... Follow the wizard to install Shared ... you can try the steps below to install Shared Fax Client: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)
Loading