Remote Control Fails with Disk Error Msg

I recently started getting the error message:

"There is no disk in the drive. Please insert a disk into drive D:" Cancel Try Again Continue

I get this when connecting to a remote control host on a server where the 24x7 software is installed on the D drive. My client is a laptop in which the D drive is a CD/DVD drive. I normally have no disc in the CD drive on the laptop but I recently had one in there and now after I take it out it continually gives this error message until it is put back in.

Thanks for your help,
Jeff

This indicates that some process is looking for files on disk D. If you are attempting to test jobs locally, it could be 24x7 that is trying to access the D disk. But there is nothing I can say for sure until more details become available. Please describe when exactly this happens and exact steps that lead to the message.

Here is the sequence of events:
1) Start 24x7 Scheduler (Remote Control)
2) Select remote host and click connect
3) Brings up logon box which has ID filled in, I always leave password blank and click OK
4) Connects to Host and synchronizes data and jobs and appears ready to show all the jobs and the error message comes up.

I am attaching a screenshot of the error, you can see that the 42 jobs have synchronized prior to the error.

I'm not sure why it needs disk D. At the moment I can only suggest to configure Windows to use a different drive letter for the CD/DVD disk, for example, use letter E. To change the letter: Control Panel -> Administrative Tools -> Computer Management -> Disk Management -> Right-click on CD drive and choose Change Drive Letter from the popup menu). This will free letter D as a device name. After that map one of the local folders as a D drive (net use D: \\machine\C$\folderD or alternatively use the Tools/Map Network Drive command in Windows Explorer). This should make the error message disppear.

FYI, just wanted to let you know. I ended up removing the CD from my computer and re-booting with the drive empty. After that I am able to connect to the remote agents fine without the request to the D drive. I'm not sure why it would behave like this, but I'm not the only one to have the problem within our company. We now know how to fix it though.

Thanks,
Jeff