GCPW Issue - Your administrator doesn't allow you to login with this account...

After installing Google Credential Provider for Windows and then proceeding to login with a Google Workspace account, one can sometimes encounter the following error message at the login screen:

"Your administrator doesn't allow you to login with this account. Try a different account"

This is often attributed to the Google Workspace admin not having added your domain to the allowed list, however, in my experience, this has never been the issue.

It seems that there can be a lag before the PC gets the correct settings sync'd from the Google cloud to the GCPW client. Manually forcing an update has always resolved things for me, at least so far. Here is the process:

- Open up the Task Scheduler on the Windows PC concerned.

- Browse through the Task Scheduler Library, then into GoogleSystem, and finally into GoogleUpdater.

- Right-click on the task named "GoogleUpdaterTaskSystem..." and choose "Run".

- Then, logout and try logging-in using a Google Workspace account.

Hopefully, this helps you.

Comments

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

WSUS Issues

Was configuring WSUS on a Server 2016 VM for a customer recently and found the performance to be very sluggish and most of the time the client PCs would time-out and throw an error message when trying to check for updates. After much digging on different forums I came across a fix that worked nicely: Open Internet Information Services (IIS) Manager and click on Application Pools Then Right-Click on your WsusPool instance and choose Advanced Settings Scroll down to Private Memory Limit (KB) and change it from the default of 1843200 to 0 which means unlimited. Then right-click and stop the WsusPool and then start it again. Hope this works for you.

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition. However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition. This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell: reagentc /disable If you get the error message "REAGENTC.EXE: Operati...

Artifact Weblog

Search This Blog