At our org we had some PowerBI/Excel stuff that required more memory than the
32 bit version can use. I never saw it personally but supposedly users would
actually get prompted by Excel that it needs more memory and they should use
the 64 bit version.
In our switch to Windows 10 the decision
My testing this afternoon would seem to confirm that the Memory Management keys
are not needed on Windows 10. At least as far as the detection script is to be
trusted. The result of the script was the same whether the keys didn't exist
(the initial state) or if they were set to enabled. If
Yea, we’ve just done that twice in the last two months to get to SQL 2016
without any problems on the ConfigMan side of things. I mean … what’s your
disaster recovery plan if you can’t reliably restore the database to a new
server?
Bryan
From: listsad...@lists.myitforum.com
> Best practices from the Microsoft PFE was to do a site migration as opposed
> to attempting to just moving the database to a new cluster.
Say what now? Tell me there’s more to it than that. Moving the DB isn’t
particularly hard. Just did it twice in the last couple of months to move to
SQL
Yes, you can skip the 1706 release and go straight from 1702 to 1710. I'd
highly recommend going that route as well.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Heaton, Joseph@Wildlife
Sent: Tuesday, December 12, 2017 1:08 PM
To:
Reporting False Patching Compliance
It does show the one server I have been working on the most as scanned
successfully with today’s date and time.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Dam, Bryan
Sent: Thursday, November 30, 2017 11:53 AM
To: mssms
I'd look closely at the scan times and states (Scan 1 - Last scan states by
collection) to verify that clients have successfully scanned for updates.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Chris Carbone
Sent: Thursday, November 30, 2017 10:41
, and another right around 1GB. Is this because WSUS
is still trying to download the Win 10 updates?
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dam, Bryan
Sent: Tuesday, November 28, 2017 8:12 AM
To:
sakt7NuoMRPjk6gJ7nkyJwbWOPG3sLWltQH-UXw=AMDEiOGN95tpVGx80k2aAiXYyWUWzHcmUu7Uxskp5j4=>
J
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dam, Bryan
Sent: Monday, November 27, 2017 3:30 PM
To: mssms@lists.myitforum.com<mailto:mssms@lis
That suggests an issue with your WSUS/SUPs. Make sure the WSUS IIS app pool
(WsusPool) is started. Then review this:
https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/
Note that the hotfixes there aren't silver bullets. WSUS
10 matches
Mail list logo
