DecemberWolf
October 5th, 2010, 09:24 AM
Hello everyone
we are looking at deploying Ubuntu desktop and laptop machines within a currently Windows based network. As we have everything running on the Active Directory, we are not able to fully migrate just yet. So far we have used likewise-open to authenticate against the AD which works beautifully and we have been able to get VPN working.
we are however stumped at the following issues, and would be very grateful for some advice on what do do!
AD home drives. we need these to map dynamically on log-in and they are not in any way standardised (i.e. being 'clever' doesn't work, we need a proper method of asking the AD what the user's home drive is. in Windows it would be "net use /home" and it maps it all!
Updates through the corporate firewall: everything I have seen would require a username and password to be left somewhere in plaintext, which we cannot allow. is there anything firewall-side we could configure to allow apt-get to do its thing, or to allow sudo credentials to be passed to the firewall when apt-get update-ing from the terminal? we have already set our domain admin group up on sudoers so the credentials would be valid.
many thanks in advance for any and all advice on this!
we are looking at deploying Ubuntu desktop and laptop machines within a currently Windows based network. As we have everything running on the Active Directory, we are not able to fully migrate just yet. So far we have used likewise-open to authenticate against the AD which works beautifully and we have been able to get VPN working.
we are however stumped at the following issues, and would be very grateful for some advice on what do do!
AD home drives. we need these to map dynamically on log-in and they are not in any way standardised (i.e. being 'clever' doesn't work, we need a proper method of asking the AD what the user's home drive is. in Windows it would be "net use /home" and it maps it all!
Updates through the corporate firewall: everything I have seen would require a username and password to be left somewhere in plaintext, which we cannot allow. is there anything firewall-side we could configure to allow apt-get to do its thing, or to allow sudo credentials to be passed to the firewall when apt-get update-ing from the terminal? we have already set our domain admin group up on sudoers so the credentials would be valid.
many thanks in advance for any and all advice on this!