Problem with DYMO CardScan executive and Outlook 2010

So the other day I ran into this issue with DYMO CardScan Executive: when attempting to "Synchronize", and choosing the Folder in question (user's Contacts), an error message would appear, and there was no way around it. It was Error creating Outlook object: “Outlook.Application”, followed by Error code 0x8002801d

Some solutions online pointed me in the direction of deleting some registry keys, but that did not solve my issue. Ultimately I turned to DYMO support who were very helpful and provided the below guide, which completely fixed the issue. This also relates to deleting registry keys, but different ones:

Error Message:

Cause:

Newer version of Microsoft Office had been installed on the computer and after removing it there are left over registry entries.

Solution 1:

Use the Windows System Restore Points and revert your system to a point when the add-ins worked.

Solution 2:

Step 1:

1.     Access the Windows Registry Editor via Start, Run, Cmd, RegEdt32, enter.

2.     Navigate to HKEY_CLASSES_ROOT\Interface\{00063001-0000-0000-C000-000000000046}\TypeLib

3.     Find a '(Default)' entry with the value '{00062FFF-0000-0000-C000-000000000046}'

4.     You should find a 'Version' entry. Check that this version matches the value in the following table based on the version of Outlook currently installed. 

Outlook Version
Outlook 2003	9.2
Outlook 2007	9.3
Outlook 2010	9.4
Outlook 2013	9.5

Step 2: (Fix the TypeLib)

1.     Navigate to HKEY_CLASSES_ROOT\TypeLib\{00062FFF-0000-0000-C000-000000000046}

2.     Delete the version keys (e.g. 9.5) for any version of Outlook that is not installed on your system based on the version table provided below. For example, if you are not using Outlook 2013 then remove the "9.5" entry. If you are not using Outlook 2010 then remove the the "9.4" entry. DO NOT DELETE the entry for the version that was configured in Step #1

3.     At the end there should be only 1 version of the Office Package in the registry.

4.     Restart the computer and reinstall CardScan.

Outlook Version
Outlook 2003	9.2
Outlook 2007	9.3
Outlook 2010	9.4
Outlook 2013	9.5

 

How to properly Failover and Failback VM replicas in VEEAM

For example in the case of Crypto virus and variants, having a good replica can save your butt.

Steps:

1. From vCentre, shut down the messed up VM in your production environment
2. In Veeam, go to Replicas - Ready, and hopefully you will find the machine in question and the restore point will be recent (but before s*** hit the fan)
3. Right click and "Failover Now", choose the correct restore point. Your machine will now power on in your DR environment and you'll find it under Replicas - Active.
4. At this point the VM can be used by users while you restore the other one from backup, or...
5. At a more appropriate time, you can "Failback" to return your Replica to the Production Cluster/Host (this will incur a downtime, length depends on the number of changes made to the VM while running in this mode).
6. Failback will either "merge" the VM to the oriignal or you can choose to Merge it to a different VM if you restored it somewhere else.
7. Users can still work until the VM powers off, it will remain powered off until disks are merged.
8. Once this is done it will power on automatically in the Production environment, at which point you can...
9. "Commit Failback" to return to normal.

Identifying the source of a User Account Lockout in a Domain

Ever get locked out of your own domain? Do your users get locked out because they logged into some PC in a remote office aeons ago and the PC has not been restarted since, so they are still logged in with their old credentials? Usually this kind of thing happens after a password change, and it can be a pain in the *** to identify which PC is locking you/user out.

Thankfully, in Windows Server 2008 and later, you can search the Event Log/Windows Logs/Security for event ID 4740 (narrowing the filter to search only the last 12 or 24 hours speeds up the process) and you should see the log entry to let you know that the account locked out.

In the entry, the Caller Computer Name is the culprit PC that needs investigating as it is locking the account out.

It could be some service running on there with incorrect credentials, or it could just be logged into Windows and came out of suspension with incorrect credentials, or the account is tied to a mapped drive...

Note that you have to enable Audit Account Management success through local DC policy or GPO on the Domain Controllers (which may be enabled by default, not sure). Instructions on how to do that are here: http://www.morgantechspace.com/2013/11/Event-ID-4740-A-user-account-was-locked-out.html

The links below go into more detail and also show how to set up email notifications to  email you when the lockout event happens.

http://community.spiceworks.com/how_to/11824-email-account-lock-out-notification

http://community.spiceworks.com/scripts/show/902-account-lockout-notification

http://blogs.technet.com/b/heyscriptingguy/archive/2012/12/27/use-powershell-to-find-the-location-of-a-locked-out-user.aspx

https://social.technet.microsoft.com/Forums/windowsserver/en-US/6052f3ca-d141-47dd-a528-02b7f4575bb5/domain-admin-account-getting-locked-outpls-help