MUST. SHARE. PAIN.
Mar. 13th, 2006 03:43 pm![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
okay.
I get a ticket from the HD. User is getting a new machine. It's not part of our contract & the non-contract tech is trying to configure it to match her contract machine which will go away.
*sigh*
So the ticket says that the user (or rather the tech working with the user) wants to know what file on her local machine does all the server drive mappings.
*blink*
I check the text to make sure I'm reading that right. *shrug* check with one of my engineers - "That's the login script, right? & it's not locally stored, it's on the server? right?" He nods. "So if the machine is connected to network & she logs in - it doesn't matter which machine, she'll still get mapped. right?" He nods again. "Okay, I'm not insane. Things haven't changed that much." (I've been doing tech support of various flavors for 20+ years - login scripts have ALWAYS resided on the server - whether unix, dos, netware or mac. but I wanted to be absolutely certain I hadn't slipped dimensions, here.)
So I call the user back. She hands me off to the tech. Who I inform that as long as the user is logging into our domain, her login script will map the drives. "But where does that script reside?" "On the server." "but how does it activate?" "She logs into the domain. Y'know, enter username, password, domain name? when she first boots up, she logs in." "so your server is constantly polling all these machines? How does it know to run that script?"
*blink*
o_0
*blink*
I smile sweetly & ask the user to hold. I look pleadingly at the engineer - my normally excellent geek-speak translation skills have apparently failed me. He decides to spare me & lets me give the guy his direct line.
I didn't catch all of the conversation but when he hung up with the guy, he went over to HIS coworker and said "So. How would YOU answer the question 'this active directory thing sounds neat - Where can I get it?'"
*headdesk*
Insert the bloody tech icon here please.
I get a ticket from the HD. User is getting a new machine. It's not part of our contract & the non-contract tech is trying to configure it to match her contract machine which will go away.
*sigh*
So the ticket says that the user (or rather the tech working with the user) wants to know what file on her local machine does all the server drive mappings.
*blink*
I check the text to make sure I'm reading that right. *shrug* check with one of my engineers - "That's the login script, right? & it's not locally stored, it's on the server? right?" He nods. "So if the machine is connected to network & she logs in - it doesn't matter which machine, she'll still get mapped. right?" He nods again. "Okay, I'm not insane. Things haven't changed that much." (I've been doing tech support of various flavors for 20+ years - login scripts have ALWAYS resided on the server - whether unix, dos, netware or mac. but I wanted to be absolutely certain I hadn't slipped dimensions, here.)
So I call the user back. She hands me off to the tech. Who I inform that as long as the user is logging into our domain, her login script will map the drives. "But where does that script reside?" "On the server." "but how does it activate?" "She logs into the domain. Y'know, enter username, password, domain name? when she first boots up, she logs in." "so your server is constantly polling all these machines? How does it know to run that script?"
*blink*
o_0
*blink*
I smile sweetly & ask the user to hold. I look pleadingly at the engineer - my normally excellent geek-speak translation skills have apparently failed me. He decides to spare me & lets me give the guy his direct line.
I didn't catch all of the conversation but when he hung up with the guy, he went over to HIS coworker and said "So. How would YOU answer the question 'this active directory thing sounds neat - Where can I get it?'"
*headdesk*
Insert the bloody tech icon here please.