Reminding me of the past 2-3 days of being very unproductive at work.
IT: Oh, you really should migrate to the new domain. Everyone needs to anyway.
ME: Fine. I'll even do some instructions for you, because there are plenty less IT-savvy people here, and you pretty much treat anyone less a network admin as a moron.
<Start using new domain>
Me: OK, I'm using the new domain, mapped all my drives, seem to be able to get to everything. A few things are authenticating oddly, and even though permissions have been copied over, they're not working as they should.
IT: <create some workaround scripts for me> (Later we find out I got my user ID too early, so my permissions weren't ported. No wonder I couldn't authenticate against databases).
Me: OK, I've backed up my email, got my archives, I know where everything is.
IT: Update me to new fancy email server.
Me: This isn't even shiny. All I've got is a fricking empty mail folder. Nirvana for some, but I'm going to have to import all the old emails to figure out what the flip I'm meant to be doing now.
IT: <silence> ... but don't let your mailbox get over 500MB
IT switches me over to some other network. I now can only get into corporate domains, not the other ones where at least half my work is. Not a permissions issue, they should all be solved now. SWEAR WORDS.
Me: <Wanders over to hassle IT, and remind them if they're nice, I have lollies and choccies on my desk. Do not remind them that I won't tell them which are the sugar-free ones, cue evil laugh>. I can't get into any of the other environments, only corporate ones.
IT: That's by design. You can now more easily access the parent company "stuff" that you could before, but it will be harder to access the other environments.
Me: But most of my work is in the other environments, not in the parent company "stuff". I could get into the parent company intranet, that's more than I need for my day-to-day job.
IT: <silence>
Me: So how do I get into the other networks?
IT: You might be able to VPN in to the other network, and work that way.
Me: But I only haven't been able to get into the other networks since you changed my port over to the new network. Does the new network see those other networks I need for work??
IT: No, and that's by design. The parent company shouldn't be able to see that.
Me: < in my head, perhaps out loud: SWEAR WORDS> So how do I get to work.
IT: <Discussions amongst the lads about sorting this out "for real" now.>
Me: <In my head: Fricking awesome, good idea to sort that out before you try to move over 200+ dev staff who won't be able to access code, builds, doco, environments ... > OK, I'll send through all URLs/servers that I know about. Can I do anything else??
IT: <Already discussing techno stuff and whatever that I don't understand>
Me: Guess I'll just go back to my desk and wait to be productive again.
At some point today, I stopped by to ask the IT guys a question. Someone said something about a B port. Eureka!!
Me: Can you enable my B port for the old network, not the new, fancy, blind to my networks one?? I have chocolate.
IT: <Fight ensues over which person will come and enable my B port>
I like our IT guys, but so often, you just need to ask the RIGHT questions to get the RIGHT answers to anticipate the problems you'll need to solve in the future.