Nozza Posted March 30, 2009 Posted March 30, 2009 Can anyone tell me how CC3 goes about mapping network drives? What I mean is how Windows actually does it underneath. So when a domain workstation is booted up how the drives are mapped. Is this set when the machine is built and then managed locally from that point or is it done by the domain controller when the machine boots up? If so, where is this managed - can I see/control this using the active directory tools on the server?
Tallwood_6 Posted March 30, 2009 Posted March 30, 2009 Drive and printer mapping is done at startup, and can be done at the location or workstation level in the RMMC and remember that interitance applies.
Nozza Posted March 30, 2009 Author Posted March 30, 2009 Drive and printer mapping is done at startup, and can be done at the location or workstation level in the RMMC and remember that interitance applies. Yes I know how RMMC handles it. What I want to know is exactly how this is effected by Windows.
sparkeh Posted March 30, 2009 Posted March 30, 2009 Drives are mapped by the RM Station Delivery App that replaces the windows mechanism. This is to deliver location specific drives and printers defined in RMMC, that the windows mechanism can't do (AFAIK). When you login, RM Station Delivery connects to AD to get information on the machines location and appropriate drives and printers are mapped (as defined in RMMC). This runs at each login, so replacing the previous drives and printers.
Butuz Posted March 30, 2009 Posted March 30, 2009 (edited) Yep - As Mark says - StnDeliv2.exe is the program that actually maps the network drives and printers during each user's log on. The RM Package name is "RM Stndeliv". If you were doing it via windows you would have to use log on scripts and it wouldn't work nearly as smoothly! Butuz Edited March 30, 2009 by Butuz
Nozza Posted March 30, 2009 Author Posted March 30, 2009 Thanks. So that app runs locally on each machine? Where does it get its info from? Is there a corresponding ini file for each workstation or something?
Nozza Posted March 30, 2009 Author Posted March 30, 2009 And where would I go to look at drive mappings there?
MattCrick Posted March 30, 2009 Posted March 30, 2009 To all intents and purposes you dont... Drive mappings and Printer allocations are all set using th RMMC. You should never need to view the backend info. If you're having problems viewing either, I'd raise a support call with RM
sparkeh Posted March 30, 2009 Posted March 30, 2009 Thanks. So that app runs locally on each machine? Where does it get its info from? Is there a corresponding ini file for each workstation or something? Yep local app that gets its info from AD
Nozza Posted March 30, 2009 Author Posted March 30, 2009 I've solved the actual issue now but I'm interested in knowing what happens. If the station delivery app gets its info from AD then I'm wondering where in AD that info is.
sparkeh Posted March 30, 2009 Posted March 30, 2009 If the station delivery app gets its info from AD then I'm wondering where in AD that info is. Interesting question and one I'm not sure answer of. Hmm perhaps take a look in the log files after login, might give some clues?: c:\program files\research machines\network management\logfiles\Station Delivery Map Drive.csv
MattCrick Posted March 30, 2009 Posted March 30, 2009 (edited) I'm pretty sure I've seen it in ADSI Edit whilst in there for RM on a support call. The info is not viewable through ADUC snappin if I remember correctly. I wouldn't advise fiddling around in there though as RM do tend to frown at that kinda thing. If you're just having problems with Drive mappings and printer allocation in one room, they'd probably advise recreating the room. Edited March 30, 2009 by MattCrick
webman Posted March 30, 2009 Posted March 30, 2009 On our locations, there are additional RM attributes beginning with rmCom2000.....
PiqueABoo Posted March 30, 2009 Posted March 30, 2009 Yep, I used the relevant attribute in a script to tell me about all the drive mappings (which is lots better than the RMMC RSI-inducing alternative). It's: rmCom2000-StnMgr-driveMappings Which holds a comma separated list of mappings for that location/station (AD OU/AD Computer object). [if you can't figure viewing that with native utils, just get SysInternals ADExplorer]
PiqueABoo Posted March 30, 2009 Posted March 30, 2009 If you were doing it via windows you would have to use log on scripts and it wouldn't work nearly as smoothly! Oh I do hope that's irony. With say Server 2008 preferences this is easy-peasy, works 100% and if it's just for a user that's how you assign it i.e. with none of the assigning drive mappings to computers, hiding and unhiding nonsense.
Oops_my_bad Posted March 30, 2009 Posted March 30, 2009 If you were doing it via windows you would have to use log on scripts and it wouldn't work nearly as smoothly! group policy preferences in 2008 probably put the RM implementation to shame!
Butuz Posted March 30, 2009 Posted March 30, 2009 Sorry - living in the past, have not even got a 2008 server here! Butuz
openaccess Posted April 7, 2009 Posted April 7, 2009 Reference for: Station Delivery Algorithm That is the Knowledge Base article on the process.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now