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

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more... but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box: \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in: UPDATE tbSingletonData SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

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.

Logon Scripts in Group Policy not running

Problem Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful. Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...

Artifact Weblog

Search This Blog