WMI Service Remote control

We need improvement on a projet to remote control an application using WMI. You would receive from us an existing code on which you need to make the improvement. Objective: Scheduling or Executing an application on a remote machine from IIS Server using IIS userid and password or using the user id which has been set in directory settings of virtual directory. Procedure: At Present we are using the following procedure to Execute an application on Remote Machine 1) Create the SAME userID and Pass in ALL the machines in which we are going to run the application with administrative rights. 2) In Directory Settings of Virtual directory, Set the userid and password which is created in all the machines. 3) Changing the Security Policy Settings in all the Computers where Windows XP is used. Using MMC open [login to view URL] . In the tree open Local Policies , Select Security options. In Network Access: Sharing and Security Model for Local Accounts Changing from Guests Only: Local Users authenticate as Guests to Classic ? Local Users authenticate as themselves. 4) We are using the following Connection string to connect to Remote Computers. Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" _ & strComputer & "\root\cimv2") Problems facing in Remote Control : 1) when connecting to remote Computer, we are getting the Error "Object Required?". For this, we have created the same user in all the computers with administrative rights. It is not working in some of the machines. 2) In Windows-XP if user has used switch user then the task is running on the context of the user who is logged in first to that machine. So the other user is not able to see the running task. What you need to do: -Improve the system so, that we can have different UserID and pass in all machines -Administrator rights should not be a MUST -we should no more get the Error "Object Required?". ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows XP, Windows 2000, Internet Explorer