Cant allocate users to lines under Windows Server 2003 (using tapimgmt.msc) ?

[Ian Clark]

Hi,

I've recently been doing some pre upgrade testing with Windows 2003 for our
2k tapi server. For some reason after installing the test rig which is
configured seperately as a DC in a seperate new forrest-domain (for
testing), installing the pbx 3rd party tspi and a generic modem for extra
sanity, then the usual process of enabling the tapi server and setting the
service account as per 2k (using tapimgmt) followed by restarting the
service (both cold boot and as prompted), the snapin still doesn't allow me
to add users to any lines on the system and the "edit user" is always
disabled on any of the lines under any of the providers ? A manual notepad
hack of tsec.ini with reboot didn't give users to lines either. Am I
missing a step here ?

Thanks

Ian

[Andreas Marschall [MVP TAPI]]

"Ian Clark" <ian.c...@btopenworld.com> schrieb im Newsbeitrag
news:uGNrG4n...@tk2msftngp13.phx.gbl...

Maybe this KB article applies to your problem:

283527 - No Built-in Groups Are Available When You Want to Give User Access to
the Telephony Server
When you try to grant user access on the telephony server, no built-in groups
are available in the Microsoft Management Console (MMC) Computer Management
snap-in. You can add only individual accounts from the Users group.
http://support.microsoft.com/default.aspx?scid=kb;en-us;283527

--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
* Please post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.

[Ian Clark]

Thanks for your response Andreas,

I've now tracked down the problem now to the tapi management snapin tool
that comes with 2K3, which looks similar to the KB article you mentioned,
although not exactly the same behaviour as I am getting.

I also have to set the tapi server to use "low security" using to allow
clients to function properly:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Serve
r\HighSecurity = 0

and then use the tapimgmt.msc from the Windows 2000 server admin pack on a
workstation which works perfectly. I expect this will be fixed soon. The
problem seems to have been introduced in the new version of the snapin,
tapisnap.dll (v5.2.3790.0) from the 2k3 tools, the 5.0.2138.1 version
doesn't have this problem.

I'd be interested to know if you have managed to get the tapi snapin to
assign users using the 2k3 tools.

Regards

Ian

"Andreas Marschall [MVP TAPI]" <Andreas....@I-B-A-M.de> wrote in
message news:%23DDqOW0...@tk2msftngp13.phx.gbl...

[Andreas Marschall [MVP TAPI]]

"Ian Clark" <ian.c...@btopenworld.com> schrieb im Newsbeitrag

news:%23ZNG6MU%23DHA...@TK2MSFTNGP12.phx.gbl...

> Thanks for your response Andreas,
>
> I've now tracked down the problem now to the tapi management snapin tool
> that comes with 2K3, which looks similar to the KB article you mentioned,
> although not exactly the same behaviour as I am getting.
>
> I also have to set the tapi server to use "low security" using to allow
> clients to function properly:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Serve
> r\HighSecurity = 0
>
> and then use the tapimgmt.msc from the Windows 2000 server admin pack on a
> workstation which works perfectly. I expect this will be fixed soon. The
> problem seems to have been introduced in the new version of the snapin,
> tapisnap.dll (v5.2.3790.0) from the 2k3 tools, the 5.0.2138.1 version
> doesn't have this problem.
>
> I'd be interested to know if you have managed to get the tapi snapin to
> assign users using the 2k3 tools.

Yes and no.
It wasn't possible to assign users to the lines available by default
(UniModem, H323 etc.).
There the "edit user" was disabled on all thoise lines..
But with a non-MS 3rd party TSP (Siemens HiPath TAPI 170) it was able to
assign users.
I didn't try whether clients actually can connect to the telephony server.