Re: Using ADSystemInfo causes "Class doesn't support Automation" Error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Peter Christopoulos (peter.christopoulos_at_originenergy.com.au)
Date: 03/03/04 

Date: Tue, 02 Mar 2004 23:08:31 -0800

Hi Richard,

Thanks for your quick response.

The 2 clients I am having a problem with are both Windows XP SP1.

The issue I have is that the logon script used to work but now it does
not, so obviously someting has changed on the PC. (The user's assure me
they did not make any changes...)

I need to now what dll's or files are being used by the ADSysteminfo
class to get the information. these files may have become corrupted on
the system or they have been overwritten by an application or update
being installed?

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Relevant Pages

  • Re: XP Pro SP1 Disabled multiple device fax sending
    ... What research convinced you that Windows XP Fax was ... What did SP1 ... > I have many other clients running VSI Fax on SCO, Sun, ... > question "what product will support concurrent faxing?" ...
    (microsoft.public.windowsxp.print_fax)
  • RE: NT 4.0 to Windows 2003
    ... Windows 2000/XP Clients? ... Domain and Forest Functional Levels only affect the DCs. ... we have to enter the name of the logon script into the Profile tab ...
    (microsoft.public.windows.server.migration)
  • Re: Windows 98 Clients and Active Directory
    ... Another way would be probably to create a logon script and write client OS, ... MVP Windows Server - Directory Services ... > Does anyone know of a way to log the clients that have logged in to the ... > Windows 98 prior to performing our Windows 2003 Active Directory upgrade. ...
    (microsoft.public.win2000.active_directory)
  • How do I assign computers?
    ... Windows 2000 Domain Controller ... Isolated test environment with one XP Pro (SP1) host ... I have discovered my clients. ... client to them from the SMS manager on my only Site. ...
    (microsoft.public.sms.setup)
  • RE: NT4 to W2K3 login scripts
    ... We cannot use Group Policy for NT4 clients. ... So if you have any Windows NT ... we have to enter the name of the logon script into the Profile tab ... This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.migration)