I have followed Microsoft's Instructions on restricting a group from sending or receiving Internet Email using a recipient policy. The recipient policy basically changes the name to something like @fakedomain.local and removes the domain fakedomain.com so the user is unable to receive Internet Email. Whe the user tries to logon using the OWA, I get no error message just the screen to logon again. I am unable to get anyone using the @fakedomain.local name to logon to the OWA. I read something about creating another virtual directory. Does anyone have any suggestions on how to logon to the OWA using a different domain name?
Hi, This should help: http://support.microsoft.com/default.aspx?scid=kb;en-us;293386 Leif "DebraH" skrev i en meddelelse news:878FA334-C970-4E99-82FD-06CE579C1120@microsoft.com... > I have followed Microsoft's Instructions on restricting a group from sending > or receiving Internet Email using a recipient policy. The recipient policy > basically changes the name to something like @fakedomain.local and removes > the domain fakedomain.com so the user is unable to receive Internet Email. > Whe the user tries to logon using the OWA, I get no error message just the > screen to logon again. I am unable to get anyone using the @fakedomain.local > name to logon to the OWA. I read something about creating another virtual > directory. Does anyone have any suggestions on how to logon to the OWA using > a different domain name?
Oh Good. I have done this. But I am unsure how to logon to the @fakedomain.local virtual directory. I do not have a domain internally. To logon to OWA, we use https://servername/exchange. I named my virtual directory local. I tried logging on using http://servername/local. I get the 401 error. what am I doing incorrectly? "Leif Pedersen [MVP]" wrote: > Hi, > > This should help: > http://support.microsoft.com/default.aspx?scid=kb;en-us;293386 > > Leif > > "DebraH" skrev i en meddelelse > news:878FA334-C970-4E99-82FD-06CE579C1120@microsoft.com... > > I have followed Microsoft's Instructions on restricting a group from > sending > > or receiving Internet Email using a recipient policy. The recipient policy > > basically changes the name to something like @fakedomain.local and removes > > the domain fakedomain.com so the user is unable to receive Internet Email. > > Whe the user tries to logon using the OWA, I get no error message just the > > screen to logon again. I am unable to get anyone using the > @fakedomain.local > > name to logon to the OWA. I read something about creating another virtual > > directory. Does anyone have any suggestions on how to logon to the OWA > using > > a different domain name? > > >
Sorry - the error was a 404. Am I to just have them use the Outlook client? This would not be advantageous since they do not stay at one terminal. "Leif Pedersen [MVP]" wrote: > Hi, > > This should help: > http://support.microsoft.com/default.aspx?scid=kb;en-us;293386 > > Leif > > "DebraH" skrev i en meddelelse > news:878FA334-C970-4E99-82FD-06CE579C1120@microsoft.com... > > I have followed Microsoft's Instructions on restricting a group from > sending > > or receiving Internet Email using a recipient policy. The recipient policy > > basically changes the name to something like @fakedomain.local and removes > > the domain fakedomain.com so the user is unable to receive Internet Email. > > Whe the user tries to logon using the OWA, I get no error message just the > > screen to logon again. I am unable to get anyone using the > @fakedomain.local > > name to logon to the OWA. I read something about creating another virtual > > directory. Does anyone have any suggestions on how to logon to the OWA > using > > a different domain name? > > >
Hi, To use OWA with an additional domain name you should connect to http://servername/name of new virtual directory. If you are using SSL that might however not work Leif "DebraH" skrev i en meddelelse news:9A115C12-FA0D-4E72-B9EF-3987F02F46D6@microsoft.com... > Oh Good. I have done this. But I am unsure how to logon to the > @fakedomain.local virtual directory. I do not have a domain internally. To > logon to OWA, we use https://servername/exchange. I named my virtual > directory local. I tried logging on using http://servername/local. I get the > 401 error. what am I doing incorrectly? > > "Leif Pedersen [MVP]" wrote: > > > Hi, > > > > This should help: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;293386 > > > > Leif > > > > "DebraH" skrev i en meddelelse > > news:878FA334-C970-4E99-82FD-06CE579C1120@microsoft.com... > > > I have followed Microsoft's Instructions on restricting a group from > > sending > > > or receiving Internet Email using a recipient policy. The recipient policy > > > basically changes the name to something like @fakedomain.local and removes > > > the domain fakedomain.com so the user is unable to receive Internet Email. > > > Whe the user tries to logon using the OWA, I get no error message just the > > > screen to logon again. I am unable to get anyone using the > > @fakedomain.local > > > name to logon to the OWA. I read something about creating another virtual > > > directory. Does anyone have any suggestions on how to logon to the OWA > > using > > > a different domain name? > > > > > >
