End User wrote:
You're in an enterprise environment...you shouldn't be trying to install it on your own. There's a reason we don't give people admin access. You don't know what sort of problems you updating will create for any management systems. For example, Configuration Manager requires an update to be able to manage new Windows 10 versions properly.
Also if you're running Win10 Enterprise that's usually not available right away. Seems like it normally takes a few weeks for an updated build to show up at the volume licensing site.
As the spring update (Creators Update?) is also problematic I'd say a) there is an issue with that workstation or b) the IT department is lagging behind on the updates.
He doesn't have administrative privileges to the workstation...there's nothing wrong with it. He mentioned in another reply that he's in a testing group for Windows 10. They're likely testing a specific configuration, so him updating would put him out of the configuration they're testing. Updating your personal machine at home is one thing, but in an enterprise environment where time is literally money, you run what your IT department has tested to be stable.
There's also the fact that they could be running on the Long-Term Servicing Branch (LTSB), which would have its own issues with updating.
End User wrote:
The IT department is lagging behind on the updates.
In corporate IT, this is a 100% given. IT people seem to get lazier and more prone to procrastination as time goes on.
It's not so much laziness and procrastination in some cases
. In my case it's that there are only so many hours in the day. I'm responsible for managing all servers, storage, switches, firewalls, software deployments, patch management, software updates, Windows deployment configuration, plus dealing with day-to-day issues. I have to prioritize what's the most important, and sometimes that simply means keeping things operational so users can work. We're still on Windows 8.1, but that's definitely not due to laziness or procrastination. I have been hard at work on getting Windows 10 ready to go, and the Fall Creator's Update will be our starting point.
IT responsibilities continue to grow, but often times the teams sizes don't. I've actually lost team members (due to state government budget issues) and it's all we can do to keep from drowning in the never ending tasks that we have to accomplish on a daily basis.
Now in other cases, it's definitely laziness. My wife works for a major clothing retailer. They were running Windows 8.1 on Dell XPS 12's until last year...and they went backwards to Windows 7 on the new laptops they purchased. I've told her for years that their IT department sucks.
End User wrote:
curtisb wrote:https://docs.microsoft.com/en-us/sccm/c ... windows-10Configuration Manager 1706
For example, Configuration Manager requires an update to be able to manage new Windows 10 versions properly.
Supported Windows 10 versions:
1703 (known as the Creators Update) Supported
1709 (known as the Fall Creators Update) Backwards compatible
Editions: Enterprise, Pro, Education, Pro Education
Backwards compatible - This means that existing client management features (hardware inventory, software inventory, software updates, etc.) should work with the new Windows 10 release. Any known issues or caveats will be documented.
Assuming they're even running SCCM, you're assuming they've upgraded to SCCM 1706. FWIW, SCCM 1706 was released to support Windows 10 1709. Windows 10 1703 was "supported" in SCCM 1702 via backwards compatibility. Full support for Windows 10 1703 wasn't available until SCCM 1706. My point still stands that new versions of SCCM are required to support new versions of WIndows 10. Full support for Windows 10 1709 won't actually come until the next release of SCCM.
They've definitely made SCCM easier to upgrade. Getting into the current branch from SCCM 2012 R2 is now an in-place upgrade, and once you're into the current branch, updates can be initiated from within the SCCM Console. There are still some steps that might need to be taken manually, like upgrading the ADK on the site server, but overall it's much easier than it used to be.
SCCM was only an example. There are many other considerations that must be taken into account, to include third-party antivirus software.