Sorry in advance if this isn't the right place. I was told I needed to post this here.
I want to overhaul my logon.bat file process that is currently using KIXTART, group membership and IP addresses to map drives. Over time the script has become more complicated and with Windows 8.1 and 10 it has become less reliable and a lot of users
have to click the logon.bat shortcut we put on their desktops. I also have a cheesy printer install script, so I would like to use GPOs to map drives and load printers.
My AD is broken out by office (8). Users within each office are then part of different security groups which gives them access to different parts of the domain. The main office is broken down even further into divisions. The majority of my
data is currently being moved to the cloud, and we have cloud caching devices at each office (why we need location mapping).
User Example
When in Office1
P: \\OFFICE1\PROJECTS
M:\\OFFICE1\MARKETING
X:\\OFFICE1\PROGRAMS
U:\\OFFICE1\USER\%username%
Printers
\\OFFICE1\PRINTER1
\\OFFICE1\PRINTER2
\\OFFICE1\PRINTER3
When in Office2
P: \\OFFICE2\PROJECTS
M:\\OFFICE2\MARKETING
X:\\OFFICE2\PROGRAMS
U:\\OFFICE2\USER\%username%
Printers
\\OFFICE2\PRINTER1
\\OFFICE2\PRINTER2
\\OFFICE2\PRINTER3
In addition to the location mappings, I also have mappings regardless of location to data that won't be in the cloud - accounting, etc. So when a user is in Office1 and the local data is in Office2, they will need to map to Office2 based on their group membership (Accounting).
Because I have the location and group membership requirements, don't see any way to use the ADMX GPO drive mapping option. Please fill me in if I am missing something! I think I will still have to run some sort of script to get everything mapped
and loaded. So, if that's the case, what is the big advantage of using a GPO?
Thanks in advance!