This was precisely how we implemented our system, only the MSS is on the corporate network. The MAS and MSS are on the private LAN, and then we have the corporate connections for the MASs on another private LAN. This allows us to be much more selective on how we implement Windows patches.
You do lose some functionality by doing this though. First, you need a way to administer the MAS, so your only two options are to either be at the console, or have some sort of IP KVM. Second, none of your users will be able to use Subscriber Options, since that requires access to an MAS. Also, if you use the web client, the MAS cannot call the users since it needs to talk to the MAS to grab a port. But the IMAP4 connection to the MSS for your Lotus client should work just fine.
Some other things to keep in mind. Your MAS servers will not have access to a DNS server, so you need to build the hosts file. Also, for some reason during install, they do need to be connected on both the corporate and private LAN. As mentioned before though, both can be private.
We've been running this way for about 18 months with no adverse affects other than those mentioned above.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.