RE: Disabling .NET Passport options in Windows Messenger v5
From: Nick (Nick_at_discussions.microsoft.com)
Date: 01/21/05
- Next message: ntman68: "Vid conference using Windows (not MSN) Messenger"
- Previous message: Jonathan Kay [MVP]: "Re: msn file 1603"
- Next in thread: Bob Christian: "Re: Disabling .NET Passport options in Windows Messenger v5"
- Reply: Bob Christian: "Re: Disabling .NET Passport options in Windows Messenger v5"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 21 Jan 2005 13:45:04 -0800
I've been trying to accomplish the exact same thing. There was a registry
key that only allowed Exchange IM connectivity for Messenger, which was
great, but now that we're testing the migration to Live Communication Server,
we don't have a way to disable .NET logon. Please help...? I'd rather block
access to the options entirely versus blocking traffic at the firewall (and
having people complaining that they configured it but doesn't work, and then
going through the IM policy with them again...)
"The_Black_Piggy" wrote:
> Hi, I wonder if anyone can provide any hints. We've got Windows
> Messenger v5 installed plus Live Communication Server. We only want
> users to be able to use WM5 internally so communication is limited to
> other staff in the company, i.e. they can only log into a SIP
> Communication Service Account. What I'm actually asking is: is it
> possible to disable all the .NET Passport account options? Or how else
> might we stop external comms?
>
> Many thanks.
>
- Next message: ntman68: "Vid conference using Windows (not MSN) Messenger"
- Previous message: Jonathan Kay [MVP]: "Re: msn file 1603"
- Next in thread: Bob Christian: "Re: Disabling .NET Passport options in Windows Messenger v5"
- Reply: Bob Christian: "Re: Disabling .NET Passport options in Windows Messenger v5"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|