F5F Stay Refreshed Software Operating Systems Users of SCCM 2012 R2

Users of SCCM 2012 R2

Users of SCCM 2012 R2

B
Baby_Pigflame
Junior Member
12
02-06-2016, 12:23 PM
#1
Yes! We implement it at the University of Minnesota in the United States. Our system has significantly more devices than ours, and we have a specialized group handling it (I’m not part of that team), but I rely on it frequently for tasks like software control, imaging, and deployments.
B
Baby_Pigflame
02-06-2016, 12:23 PM #1

Yes! We implement it at the University of Minnesota in the United States. Our system has significantly more devices than ours, and we have a specialized group handling it (I’m not part of that team), but I rely on it frequently for tasks like software control, imaging, and deployments.

O
OGStewy
Junior Member
22
02-07-2016, 11:10 PM
#2
We handle administration, packaging, and deployments for our customers. You don’t typically manage corrupt clients or troubleshoot issues—our focus is on delivering and supporting software releases.
O
OGStewy
02-07-2016, 11:10 PM #2

We handle administration, packaging, and deployments for our customers. You don’t typically manage corrupt clients or troubleshoot issues—our focus is on delivering and supporting software releases.

P
pir4ta_extreme
Junior Member
8
02-08-2016, 09:24 AM
#3
P
pir4ta_extreme
02-08-2016, 09:24 AM #3

W
WasianNinja
Member
174
02-08-2016, 04:33 PM
#4
Absolutely, most of the time refreshing the machines works best. Occasionally the Config Manager client gets corrupted, which usually resolves itself when you uninstall and reinstall. If WMI becomes damaged, simply clearing it out is often the solution. It might also be worth mentioning that AD could be involved in the discussion. I don’t handle our AD setup directly, but I use it regularly to verify everything is placed correctly for policies and similar tasks.
W
WasianNinja
02-08-2016, 04:33 PM #4

Absolutely, most of the time refreshing the machines works best. Occasionally the Config Manager client gets corrupted, which usually resolves itself when you uninstall and reinstall. If WMI becomes damaged, simply clearing it out is often the solution. It might also be worth mentioning that AD could be involved in the discussion. I don’t handle our AD setup directly, but I use it regularly to verify everything is placed correctly for policies and similar tasks.

D
Dashel
Member
55
02-15-2016, 02:48 PM
#5
Is there a reimaging process in place, or can you boot any system directly to reimage whenever needed? It seems likely they rely on a standard PXE password.
D
Dashel
02-15-2016, 02:48 PM #5

Is there a reimaging process in place, or can you boot any system directly to reimage whenever needed? It seems likely they rely on a standard PXE password.

J
jaloks
Junior Member
32
02-15-2016, 07:44 PM
#6
Mostly handled through a ticketing platform, with multiple support levels and staff where tickets move between tiers and campus areas based on the issue or duties. For imaging, I typically take the device back to my office for reimaging so I can monitor it closely and apply any needed software. I believe your organization also relies on a similar system (though I doubt support would function effectively without one in a large company).
J
jaloks
02-15-2016, 07:44 PM #6

Mostly handled through a ticketing platform, with multiple support levels and staff where tickets move between tiers and campus areas based on the issue or duties. For imaging, I typically take the device back to my office for reimaging so I can monitor it closely and apply any needed software. I believe your organization also relies on a similar system (though I doubt support would function effectively without one in a large company).

B
BlaizenBoy
Member
157
02-16-2016, 04:06 AM
#7
We also face a frustrating, very slow ticketing system. I've been considering creating unique PXE passwords for each of our 40+ locations. This would allow a technician to instantly know they need something instead of having to "request" it, which feels inefficient. (I was wondering if you're doing something comparable to gather real-world insights.) Probably there are benefits to testing it in paper form too.
B
BlaizenBoy
02-16-2016, 04:06 AM #7

We also face a frustrating, very slow ticketing system. I've been considering creating unique PXE passwords for each of our 40+ locations. This would allow a technician to instantly know they need something instead of having to "request" it, which feels inefficient. (I was wondering if you're doing something comparable to gather real-world insights.) Probably there are benefits to testing it in paper form too.