User Profile
--BF--
Copper Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Frequent Event Log errors related to GPO
We currently have 3 different versions of Server in our environment. 2016 2019 2022 All the 2016's and 2019's have multiple Application event log errors with the following: "Security policies were propagated with warning. 0x57 : The parameter is incorrect." When I launch RSOP.MSC on the system with the error, I can see that there is a warning under “Computer Configuration”. Going into the properties it tells me that the Warning is within the Security Settings. Drilling down into Security Settings, I can see that the Password Policy has some issues. The 2022's don't have this issue. All systems use the same "Default Domain Policy" When I enable winlogon.log via the registry settings, I can see it's logging an error but it's not really giving me a clear indication what the actual problem is. Any advice how to proceed next would be greatly appreciated. Thanks!Re: Office Bug: Slow Saves on Shares
Yes, adjusting the permissions was the bandage at the end of the day. We had compared the file/folder (NTFS) permissions at length between slow and fast. It wasn't until we looked at the share permissions (as mentioned we almost always set it to give full control to Authenticated Users) that we noticed the difference. It actually was by luck that we had a share or 2 "incorrectly" set from how we normally have it. Yes, we had looked at the GPO as well and nothing jumped out while we were troubleshooting The "Fix" we found defies logic. The users are set for "Full Control" on the share. Then it takes a long time to save and the "ACCESS DENIED" comes up in Procmon...yet it still eventually saves. It's when we remove "Full Control on the share is when there are no issues. One would think the opposite should be true. If this was a server permissions issue, the user should not be able to save at all. It's binary. Either the user can or can't. However, in this case, they can....but they have to wait. What??!! Again, only Office products are affected. Same document and share with WordPad, no issue.Office Bug: Slow Saves on Shares
Our environment: Clients: Mostly Win10 22H2 with a few still < 22H2. Some Win11 on the latest build File server: VMWare Server 2019 1809 with several different volumes with a mix if NTFS and ReFS Word: Version 2303 (Build 16227.20258) Users do not have admin permissions to their own PC. For some time, we have been getting reports from our users that saving Word docs takes a very long time to complete on our file server. The odd thing was it was only certain shares where this issue took place. It was a mix of shares on NTFS and on ReFS. We discovered it’s not only Word but all Office products that we have tried. (Excel, Word, and PowerPoint). The symptom was consistent in specific locations on our file server. Open a Word doc, make a quick change, save, wait ~30 seconds while the popup says it’s saving, then it finally completes. While in other locations you do the same thing and it is instant. Does not matter if it’s a new doc or an old one. Also note we experimented on many different clients and the results were always the same. One volume was really a head scratcher. There were 2 different shares on the same volume, one the Office saves took 30 seconds while the other was instant. If you moved or copied the files between shares, it didn’t matter. It appeared to be the location that was the issue. Mind you no other issues were observed. It was only Office products. We could actually open the slow save Word doc in WordPad and it would save instantly. Try again in Word, 30 second wait. Same with .RTF files. The file type didn’t seem to matter. It was only if we used an Office product where we would see the 30 saves. We discovered that if we added the user to the server’s admin group, the 30 second save would go away! Fired up Procmon and did a winword save comparison between the two type of saves. The 30 second save had an “ACCESS DENIED” right before the long wait. (See pics). The Procmon output for the instant saves did also try to do the "Write DAC, Write Owner" but it was successful. After many days of troubleshooting, we finally found a “fix”. Most of our shares are setup up where the authenticated users group is in the “Share Permissions” with full control. From there we rely on the NTFS permissions to allow/deny access to various parts. This is what we have been doing for many years without incident. It turns out if we uncheck the allow “Full Control” and leave “Change” and “Read” checked, the Office saves are now instant! I would like to stress that we have tried several different things and the issue was always with Office products and nothing else. If feels like there was some sort of Office patch that has caused this issue since this seemed to suddenly occur across the board with no warning. ThanksRe: Windows Admin Center Access Denied
Yeah, I got a new laptop at work (Win 10) and getting WAC going again was a major test of patience. If the user has local admins, not a problem. But we use our PC's with regular user rights and then have a privileged account that we use as needed. In almost all cases, when installing an app, with the prv account on our PC's, it's not a problem. Next time it runs, it prompts for the prv, I give it the prv finger and life goes on. Easy Peasy. Even trying to install it while under my prv account, it still fails initially when using this with my regular account. I again had to put my regular account into the local admin group, then launch WAC so that it could get whatever backend bits tacken care of, then remove myself from local admins. No other administrative application we use has such hoops to jump through. Now it does work under my normal account but still need to manually log in to at least one of the systems on my WAC list with my prv account since they all try to use my non-prv account. Very much a pain since my prv account's password is quite long. This solution is very much NOT non-admin profile friendly at all. If it would just work so that we can use Windows Hello prv account signon at launch like 95% of everything else on my laptop, this thread wouldn't exist. Anyone know of a better alternatives than WAC?Re: Windows Admin Center Access Denied
Well today is a new day and after firing up WAC, I'm greeting with the same issue again. Perhaps I'm not looking at this correctly. Having to add my non-prv account to the admin group, log in, run WAC, remove my non-prv account from admin, log out, log back might be a feature?SqlServer PS module and SQLPS Clarification
I've already started a thread last week about this on the SQL MSDN forums and have not gotten anywhere. So I'm hoping that since this might be more of PS thing, maybe you fine folks could shed some light. I understand that SqlServer has replaced SQLPS. I experienced this with SQL 2017. I'm now putting together a SQL 2019 with Server 2019 and I see that SQLPS is still part of the install. PS C:\Windows\system32> get-module sqlps -ListAvailable Directory: C:\Program Files (x86)\Microsoft SQL Server\150\Tools\PowerShell\Modules ModuleType Version Name ExportedCommands ---------- ------- ---- ---------------- Manifest 15.0 SQLPS {Backup-SqlDatabase, Save-SqlMigrationReport, Invoke-Polic... Before I do an install of SqlServer module, is it advised to uninstall SQLPS first? I did try to install SqlServer without trying to remove SQLPS and I'm then presented with all sorts of red text PackageManagement\Install-Package : The following commands are already available on this system:'Add-SqlAvailabilityDatabase,Add-SqlAvailabilityGroupListenerStaticIp,Add-SqlFirewallRule,Backup-SqlDatabase,blah blah blah....'. This module 'SqlServer' may override the existing commands. If you still want to install this module 'SqlServer', use -AllowClobber parameter. Should one just -AllowClobber? When I do that, both SQLPS and SqlServer appear to be installed. Someone from that SQL forum did suggest to uninstall SQLPS. However, that brings up more issues. I attempted to Uninstall-Module and Remove-Module with no luck. PS C:\Windows\system32> Uninstall-Module -Name sqlpsPackageManagement\Uninstall-Package : No match was found for the specified search criteria and module names 'sqlps'. At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:2194 char:21 + ... $null = PackageManagement\Uninstall-Package @PSBoundParameters + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Microsoft.Power...ninstallPackage:UninstallPackage) [Uninstall-Package] , Exception + FullyQualifiedErrorId : NoMatchFound,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage and PS C:\Windows\system32> Remove-Module -Name "SQLPS" Remove-Module : No modules were removed. Verify that the specification of modules to remove is correct and those modules exist in the runspace. At line:1 char:1 + Remove-Module -Name "SQLPS" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ResourceUnavailable: (:) [Remove-Module], InvalidOperationException + FullyQualifiedErrorId : Modules_NoModulesRemoved,Microsoft.PowerShell.Commands.RemoveModuleCommand From what I can tell online, remove-module needs quotes while uninstall-module does not. Please advise and thanks!
