Running IVM on Windows 2003 Server

[santiagokid]

I have been working with IVM to develop a basic voicemail system that forwards voicemails to my email. I have a simple network running in my small office that uses Windows 2003 as a Domain controller, DNS and application server, which serves Quickbooks. I had the great idea of dropping in about three modems to handle voicemail and faxes. One modem handles faxes through MSFax. The other two modems provide voicemail support for two lines.

 

The system works great, as long as no one is logged in via Remote Desktop to use Quickbooks. I found out that if you are the Admin, logged in locally, or if no one is logged in, the system works great. However, if I have one user logged in via RDP, then the voicemail system won´t answer properly.

 

I have IVM set up as a service and run before login. However, every person that logs in has IVM running as a process in their session. I am assuming that is causing the problems.

 

How can I get IVM to run only for the Administrator and not automatically load for each user that uses terminal server? I tried placing the IVM setup file in the Administrator's files directory, but the unzip folder does not have the same restrictions, so it get's installed for every user regardless of the main file's location. Is there a version where I can specify the unzip location?

 

I only want one copy running at any one time, if anyone can suggest something, that would be great.

 

Thanks,

 

santiagokid

[mchristsen]

I am also running IVM on Windows 2003 Server. I have found that when a connection is made through RDP, the sound cars setting are changed in the shell environment from your Modem or Sound Card to RDP Sound Device. This is because RDP is trying to pipe the sound from the server to the Remote Desktop.

 

IVM responds to this change, by changing its Playback and call announce sound device properties (File -> Settings -> Device). I don't know if blocking IVM from running in the RDP session will fix this (I think it might). An alternative woould to have IVM running on a different machine (I have IVM running on my second DC) or to have Quickbooks data files located on the server and users run the Quickbooks app on thier machines (I do this with MS Money).

 

I hope this sheds some light on the situation.

 

Mike.

 

I have been working with IVM to develop a basic voicemail system that forwards voicemails to my email.  I have a simple network running in my small office that uses Windows 2003 as a Domain controller, DNS and application server, which serves Quickbooks.  I had the great idea of dropping in about three modems to handle voicemail and faxes.  One modem handles faxes through MSFax.  The other two modems provide voicemail support for two lines.

 

The system works great, as long as no one is logged in via Remote Desktop to use Quickbooks.  I found out that if you are the Admin, logged in locally, or if no one is logged in, the system works great.  However, if I have one user logged in via RDP, then the voicemail system won´t answer properly.

 

I have IVM set up as a service and run before login.  However, every person that logs in has IVM running as a process in their session.  I am assuming that is causing the problems.

 

How can I get IVM to run only for the Administrator and not automatically load for each user that  uses terminal server?  I tried placing the IVM setup file in the Administrator's files directory, but the unzip folder does not have the same restrictions, so it get's installed for every user regardless of the main file's location.  Is there a version where I can specify the unzip location?

 

I only want one copy running at any one time, if anyone can suggest something, that would be great.

 

Thanks,

 

santiagokid

<{POST_SNAPBACK}>

[Guest Guest_Santiagokid_*]

Mike,

 

Thanks for the reply. I found a workaround using software restriction policies. I have the software run only for local admins and that seems to solve the problem.

 

Regards,

 

Steve

 

I am also running IVM on Windows 2003 Server.  I have found that when a connection is made through RDP, the sound cars setting are changed in the shell environment from your Modem or Sound Card to RDP Sound Device.  This is because RDP is trying to pipe the sound from the server to the Remote Desktop.

 

IVM responds to this change, by changing its Playback and call announce sound device properties (File -> Settings -> Device).  I don't know if blocking IVM from running in the RDP session will fix this (I think it might).  An alternative woould to have IVM running on a different machine (I have IVM running on my second DC) or to have Quickbooks data files located on the server and users run the Quickbooks app on thier machines (I do this with MS Money).

 

I hope this sheds some light on the situation.

 

Mike.

<{POST_SNAPBACK}>

[CAConnell]

I am also running IVM on Windows 2003 Server.  I have found that when a connection is made through RDP, the sound cars setting are changed in the shell environment from your Modem or Sound Card to RDP Sound Device.  This is because RDP is trying to pipe the sound from the server to the Remote Desktop.

<{POST_SNAPBACK}>

 

Mike,

 

I'm not using 2003 but WindowsXP Pro. This version acts as a RDP server for only one concurrent connection. I've found that on the RDP client, if I change the "Local Resources" - "Computer sound" option to "Do not play" I no longer have the problem you describe.

 

I'm going to investigate Steve's solution (which I like better than mine). I'm not as versed on policies, but I'll soon learn.

 

Chris

[mchristsen]

Mike,

 

I'm not using 2003 but WindowsXP Pro. This version acts as a RDP server for only one concurrent connection. I've found that on the RDP client, if I change the "Local Resources" - "Computer sound" option to "Do not play" I no longer have the problem you describe.

 

I'm going to investigate Steve's solution (which I like better than mine). I'm not as versed on policies, but I'll soon learn.

 

Chris

<{POST_SNAPBACK}>

 

You are correct. Also, "Leave at the competer" should also work.

[mdkinc]

Try going to start run mstsc /console

 

That logs the remote into the session running on the server.

 

If you don't then rdc is in a seperate session and will cause many issues.

 

Max