![]() 07/13/2015 at 23:13 • Filed to: Snapchat | ![]() | ![]() |
I.... I got nothing more to say.
![]() 07/13/2015 at 23:22 |
|
We rolled out office 2013 the last couple weeks. In the email it said the old shortcuts you made won’t work. Out of 400 people we got 50 my shortcut isn’t working.
![]() 07/13/2015 at 23:24 |
|
Did you tell the to take the long way around? I wouldn't be able to resist that.
![]() 07/13/2015 at 23:25 |
|
Why didn’t roll out the new shortcuts? What version did you come off of? I mean, come on IT guys! It’s a one liner script (assuming SCCM and not GP pushes, if GP pushes... WHY!?!?!?!)
![]() 07/13/2015 at 23:25 |
|
“Hey boss, they shipped us upside down ones again”
![]() 07/13/2015 at 23:26 |
|
The mail described how to delete and really pin apps to the taskbar. There is no excuse. I’m on call at the moment, so expect to get some calls night.
![]() 07/13/2015 at 23:28 |
|
I had no luck removing the user placed shortcuts. Rolling out via sccm. 2010 to 2013.
![]() 07/13/2015 at 23:29 |
|
You should have brought a weed wacker & machete in, next time be like,
I’m ready to make a short cut for you!!
![]() 07/13/2015 at 23:30 |
|
Ah, yes. User created shortcuts are another beast! Doable, but a little too taxing to be reasonable I think.
![]() 07/13/2015 at 23:31 |
|
Also our testing group may be too advanced. We didn’t run into issues until it was Bob in sales that pinned 40 spreadsheets to his desktop.
![]() 07/13/2015 at 23:32 |
|
I know I walked by that box more than 3 times. I finally decided to do something about it, share with the rest of my coworkers on other jobs how dumb my coworkers are.
![]() 07/13/2015 at 23:37 |
|
Just leave this on a shared drive and tell them to run it (powershell)
cd $env:userprofile\desktop
gci -filter *.lnk | remove-item
There, all your shortcut are belong to me! Feel free to replace what you use ;)
![]() 07/13/2015 at 23:38 |
|
LOL, of course it was sales! I’m face palming for you here.
![]() 07/13/2015 at 23:41 |
|
Didn’t want to go whole hog, still have users with visio etc. So we just mark the tickets with “user did not read instructions” and apply to their HR file.
![]() 07/13/2015 at 23:45 |
|
But. It’s basic instructions. People still amaze me.
![]() 07/13/2015 at 23:45 |
|
LOL, Ouch!
If I was serious I’d just loop through the child items and compare the values to an array with office.lnk, excel.lnk etc... But I’d probably have a scary version for certain people / situations.
![]() 07/14/2015 at 00:03 |
|
It’s an easy way for managers to see if employees are performing, and also a way of us justifying the cost hole that is it.
I’m iffy at powershell, but I could pull it off, but it would take longer than the tickets. I’m also supporting storage, virt, voip, servers, etc...so it’s a cost/benefit /annoyance problem too.
![]() 07/14/2015 at 00:13 |
|
I’m a “developer” of sorts (strange job title, but code and scripts is a huge part of it) and I LOVE PowerShell. I have written PowerShell script to do essentially SCCM’s work during rough times (Push, install, check and report) and something like that is easy peasy. I’d encourage anyone in IT or IT-ish field to get at least to proficient because the cost benefit for a 3 liner or so (All that would take to work 99% of the time) would be worth it (If it weren’t for your HR process).
At my old company something similar was mentioned a few times and we struck it down, it wasn’t the relationship I and most of us wanted. Sure we got a lot of stupid tickets / calls etc. but as it was no one ever reported the important stuff and we had too many departments with money who thought they could just up and buy software / hardware and we’d get it to work for them, we didn’t most the time but the strain of chasing down all the cogs that “approved it” .
Getting WAY off topic now though, lol.
![]() 07/14/2015 at 00:24 |
|
Nice. We’ve been trying to hire a developer for over a year. Either it’s not enough experience or management thinks it’s not worth what it is. Supporting 1000 devices with 6 people here.
![]() 07/14/2015 at 00:26 |
|
And I’m not that bad at PS. I really only use it for administering apps.
![]() 07/14/2015 at 00:31 |
|
No idea where you are, but finding a company isn’t any better. Everyone wants mid-sr. level experience and to pay for entry level where I was, so I moved back north-ish (Still Mid-West) and did better.
![]() 07/14/2015 at 01:08 |
|
Wish I got an email like that when we rolled out Office 2013. Because yeah, it took a while before I realized my pinned shortcuts wouldn’t work anymore. After the fact I mentioned something to the IT guy and he was all like, “oh yeah that’s how it works when we upgrade” and never did it occur to him that maaaaybe he should’ve told us that before doing the upgrade.
![]() 07/14/2015 at 01:23 |
|
![]() 07/14/2015 at 07:47 |
|
Hey, me too! I freakin’ love PowerShell. My current position is administering field servers (about 5,000) but most of the time I find myself fixing the deployment and dev’s code so their product actually gets pushed right.
![]() 07/14/2015 at 08:04 |
|
Sounds like we have similar jobs. I use a fair amount of AutoIt and powershell to make tools to do things.
![]() 07/14/2015 at 10:24 |
|
LOL, I have a deep loathing for AutoIT it though!
But it isn’t AutoIT’s fault, its that I always saw it used for the weirdest things where GP or education was the real problem and then I would find 500 compiled AutoIT scripts that needed to be “updated” which really meant deleted because the alternative was re-writing 500 AutoIT scripts that someone had lost the original source code for just so someone could change the Windows stack taskbutton behavior or something...
But yeah, I used PS, Batch, C# and C++ all the time in that job.
![]() 07/14/2015 at 10:40 |
|
Yeah it seems like it really encourages bad programming practices but it plays well with others. I’d have done a lot of work manually here without it.