Excellent video, DP! This will con in handy when I am on a network that allows Registry editing. Right now, both networks have lockdowns on the users...
Hi Daniel, I'm a bit late to the party in discovering your site with its wealth of information. Great video about 'Microsoft Office Trusted Documents & Locations'. Its clarity was such that I was able to listen to it like a Podcast, and follow your explanation, while on a Christmas after lunch walk. When I got back I viewed it while looking at the script and about 17mins in found one thing that's puzzled me. About half way down, within the check to see if the Key already exists, there are these statements: If sOverWriteExistingTL = "New" Then sKeyName = sKeyName & GetNextKeySequenceNo(oRegistry, sParentKey, sKeyName) End If oRegistry.DeleteKey HKEY_CURRENT_USER, sParentKey & "\" & sKeyName End If So, you've got the next key sequence number (because sOverWriteExistingTL = "New"), and it would seem that the next statement executed after 'sKeyName = sKeyName & GetNextKeySequenceNo(oRegistry, sParentKey, sKeyName)' will be 'oRegistry.DeleteKey HKEY_CURRENT_USER, sParentKey & "\" & sKeyName' But does that not mean that the script will try to delete a 'New' key which has not yet been created? Or am I missing something? I'm in the UK and am in the process of sorting out the trusted locations for an accde file. Tks
Daniel, thanks, as usual, very good information! Following you from Down Under in Queensland, Australia.
Excellent video, DP! This will con in handy when I am on a network that allows Registry editing. Right now, both networks have lockdowns on the users...
Exactly. The vbscript can also be the type of thing you hand to the IT department to implement as part of their user startup routines.
Hi Daniel,
I'm a bit late to the party in discovering your site with its wealth of information. Great video about 'Microsoft Office Trusted Documents & Locations'. Its clarity was such that I was able to listen to it like a Podcast, and follow your explanation, while on a Christmas after lunch walk. When I got back I viewed it while looking at the script and about 17mins in found one thing that's puzzled me.
About half way down, within the check to see if the Key already exists, there are these statements:
If sOverWriteExistingTL = "New" Then
sKeyName = sKeyName & GetNextKeySequenceNo(oRegistry, sParentKey, sKeyName)
End If
oRegistry.DeleteKey HKEY_CURRENT_USER, sParentKey & "\" & sKeyName
End If
So, you've got the next key sequence number (because sOverWriteExistingTL = "New"), and it would seem that the next statement executed after 'sKeyName = sKeyName & GetNextKeySequenceNo(oRegistry, sParentKey, sKeyName)' will be 'oRegistry.DeleteKey HKEY_CURRENT_USER, sParentKey & "\" & sKeyName'
But does that not mean that the script will try to delete a 'New' key which has not yet been created? Or am I missing something? I'm in the UK and am in the process of sorting out the trusted locations for an accde file.
Tks
That's right, it will delete the entry if it already exist so we start with a blank slate.