2010

Create a Group Policy to Delete these keys

[-HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Resiliency\DisabledItems]
[-HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Resiliency\DisabledItems]
[-HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Excel\Resiliency\DisabledItems]

 

2013

The above does not work for 2013 and this key needs to disable mssphtb.dll ( Windows search for Outlook 2010 ) 

You will need to find your Outlook Add In name for the below ( I have used WorksiteEmailManagement.Connect )

If you install the plugin it should be listed in 

HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins

Add the following Registry Key which adds the same behaviour as if the user had chosen “Always enable this add-in” from the dialog shown above:
Warning: These steps involve modifying the Windows Registry. Exclaimer strongly recommend backing up the Windows Registry before making any changes to it.

  1. Launch Windows Registry Editor
  2. Navigate to the following path in the tree on the left: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Resiliency\DoNotDisableAddinList
  3. Using the pane on the right, right-click and from the menu select New, DWORD (32-bit) Value
  4. Enter the name as WorkSiteEmailManagement.Connect
  5. Double-click the entry to edit it
  6. Set the value to 1
  7. Close Windows Registry Editor

 

Add the following Registry Key which adds the same behaviour as if the user had chosen “Always enable this add-in” from the dialog shown above:
Warning: These steps involve modifying the Windows Registry. Exclaimer strongly recommend backing up the Windows Registry before making any changes to it.

  1. Launch Windows Registry Editor
  2. Navigate to the following path in the tree on the left: HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\WorkSiteEmailManagement.Connect
  3. Using the pane on the right, right-click and from the menu select New, DWORD (32-bit) Value
  4. Enter the name as LoadBehavior
  5. Double-click the entry to edit it
  6. Set the value to 3
  7. Close Windows Registry Editor
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I tried to delete a stuck file in Explorer which produced the error 

Could not find this item , This item is no longer located in xxxxxx

I tried to user Command prompt, file unlocked and reboot the server to see if System had locked the file all unsucessfully.

In the end I have to use command prompt to rename the Parent Folder of the file

ren “Parent Folder Name” “Test”

This cleared and removed the file if not you should be able to delete this in Comand prompt and explorer , I was then able to rename this folder back or delete the folder if needed.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

In Office 365 when trying to Release selected message and allow Sender in the Exchange Administration portal is shows the following error

“You don’t have permission to open this page. If you’re a new user or were recently assigned credentials, please wait 15 minutes and try again”

It does allow you to just release messages. The issue is the user needs to be a Member of Hygiene Management and Organization Management Roles in 365  ( Under Permissions and Admin Roles ) 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

You can make a change to the WorkSpace description (add a full stop to the description or other characters), save it, and then reverse the change, and save it, it to force a WorkSpace to be re-indexed.

This will update the time stamp on the WorkSpace and the Indexer should pick it up to be indexed.

WorkSite Connector service is only looking for the EDITWHEN or EDITPROFILEWHEN column in the MHGROUP.DOCMASTER table

https://support.imanage.com/forums/showthread.php?t=1660&highlight=workspace

 

If changing this does not get this Workspace in the indexer it seems your connector might be broken , make sure you update to the latest version ( connector.jar )

 

 

If you have a batch of workspaces you can also do this through SQL:

To check if you are running UTC go to the below registry path on your iManage Servers
HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\WorkSite\imDmsSvc
UTC In Use = N
Or:
UTC In Use = Y

If this key does not exist 

Run this query in SQL

SELECT 'GETDATE() ', GETDATE(); 
SELECT 'GETUTCDATE() ', GETUTCDATE();

Check both the times , and update a workspace name ( by adding a full stop at the end and deleting ) and then use a select query to see which time is closer to see if it’s using UTC or not

SELECT *FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'


Check the PRJ_NAME matches your WorkSpace Description.

If you are UTC In Use = N, ( not ) use the below.

To update the WorkSpace for re-indexing:

UPDATE MHGROUP.DOCMASTERSET EDITPROFILEWHEN = GETDATE()FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'

If you are UTC In Use = Y, ( Yes ) use the below.

To update the WorkSpace for re-indexing:


UPDATE MHGROUP.DOCMASTERSET EDITPROFILEWHEN = GETUTCDATE()FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

 

I tried to use VMwares Article : https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027206

However this command was giving me nothing : vmkload_mod -s HBADriver |grep Version

I had to use the command:

 
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -d

I can see the names of the NIC, here: vmhba3 and vmhba4

With the command: 

 
/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -l -i vmhba4/qlogic

I can see this information:

  • Name: QMH2562
  • Firmware 8.01.02
  • Flash firmware level: 7.03.00
  • Bios: 3.24
  • Driver version: 2.1.27.0
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)

I recently tried to login to a service which uses the Google Mobile App for 2 Factor Authentication and it suddenly stopped working after no apperent change.

The account was still activated on my phone. I had rcently I travelled to a city with -1  hour time difference and the Time Zone had been set incorrectly back on my phone so I had to set it to manual. 

Since generating 2FA codes relies on an agreed time between your device and the third party server, having the wrong time (or timezone) on your device can cause incorrect codes to be generated, which might explain why you’re having difficulty logging in.

Fixing the Automatic Time on my phone fixed this! 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

image41Been working on a IBM X3550 M4 Server. When trying to login to this server using Internet Explorer 11 the pages refresh and just takes me back to the login screen!

This still does not work if I add the IMM site to Trusted Sites or Compatibility mode

Next I try Google Chrome which Logs me in  however this does not use the JAVA integration so I can’t use the Remote Management Java interface to control the server

Next I install Firefox which Logs me in and lets me launch the Java Applet ( Once I have added this to Permitted sites in Java Control Panel Security ) however I am greeted with an Error

AvctIBMviewer.jar invalid character in hostname

Turns out it does not like me to refer to the Ilo via DNS name ( Maybe because it has an _ in the name )

Once I use the IP , I can launch the server Ilo 

Once the IMM Firmware is updated to 5.8 I can login to IMM with Internet Explorer 11

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

 

Use this command on the host to check for Power-On Reset Errors

grep vob.scsi.scsi.scsipath.por /var/log/vobd.log

e.g.

Note – ESXi uses UTC for its timezone so minus 5 hours to match EST

These should corrolate with Event log

Source multiple Errors/ Disk and LSI_SAS

“need to be taken offline to perform a Full Chkdsk”

Resolution

Migrate machine to new host to still see it happens and update all firmware and Vmware version before Vmware Support tell you to! 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I got errors

Height: The attribute logo.height has an invalid value.
Width: The attribute logo.width has an invalid value.

Per here : https://developers.google.com/structured-data/rich-snippets/articles

Logos should have a wide aspect ratio, not a square icon.
Logos should be no wider than 600px, and no taller than 60px.
Always retain the original aspect ratio of the logo when resizing. Ideally, logos are exactly 60px tall with width <= 600px. If maintaining a height of 60px would cause the width to exceed 600px, downscale the logo to exactly 600px wide and reduce the height accordingly below 60px to maintain the original aspect ratio.

I resized my site logo to under 60PX and all was well 🙂

 

If you are getting “A value for the image field is required” it means you need to upload a thumbnail to the blog post which can be found in the settings options of the Post

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: +3 (from 3 votes)

One Way without Restart Service

I’ve come across a great way of resetting a SQL server “sa” password if you don’t have it, don’t have an account with sufficient privileges to reset it via SSMS, and most importantly, don’t have to stop the SQL services so processing can continue.fkgqx81huis863c-medium1

All you will need is psexec  (in the sysinternals  toolkit) available here à https://technet.microsoft.com/en-us/sysinternals/pxexec.aspx

Once the tools are extracted to a directory on the server:

Psexec.exe –s –i “{full path to the ssms.exe”}

This will start the SQL Management Studio as the NTSERVICE\SYSTEM account … enter the name of the SQL Server (or localhost) and then you’re in … reset the sa password in there

 

Another way

 

  1. Stop SQL Server Service
  2. Start is with 
    net start MSSQLSERVER /m"SQLCMD"
  3. sqlcmd -SServerName\InstanceName
  4. CREATE LOGIN RecoveryAcct WITH PASSWORD=’TempPass1’
    GO
  5. SP_ADDSRVROLEMEMBER RecoveryAcct,SYSADMIN
    GO
    This was on Microsoft SQL Server 2008 (SP2) – 10.0.4067.0 (X64).
     
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)