Thursday, March 6, 2008

Adjustments needed to make a Bomgar box work on an XP Pro machine in a workgroup

I just got a Bomgar box, www.bomgar.com, and I wanted to keep track of the changes needed to make an XP Pro box in a workgroup work with Bomgar. Here are the simple instructions with a screen shot of what the final setting should look like:

click ‘Start’ >> ‘Run’ >> type ‘secpol.msc’, once the security policy tool opens, drill down to ‘Security Settings’ >> ‘Local Policies’ >> ‘Security Options’, and finally ‘Network access: Sharing and security model for local accounts’.


Set it to Classic so it looks like this:

Sunday, March 2, 2008

Switching primary monitor on a laptop with an ATI video card

  1. Go to Start Menu->Control Panel.
  2. Either click on "Display" if present or "Appearance and Themes" then "Display" (if you are in category view).
  3. Click on the "Settings" tab.
  4. Click "Advanced".
  5. Click the "ATI Displays" tab (if this tab is not present you should update your video drivers).
  6. Switch the monitors labeled "1" and "2" by clicking the "1" where the "2" is selected or vice versa.
  7. Press "Apply" to apply your change.

Monday, February 18, 2008

Word template, normal.dot, can still get corrupt

It had been a while since I had seen a corrupt normal.dot until yesterday. Word would only open in safe mode and I got this error in the application event log:

event id 1000

Faulting application winword.exe, version 11.0.8202.0, stamp 47420667, faulting module winword.exe, version 11.0.8202.0, stamp 47420667, debug? 0, fault address 0x008dd26c.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

All I did was delete the user's normal.dot and then it was fixed.

Wednesday, February 6, 2008

storing Office CD key in setup.ini file

Doing Office installs became so much easier when I found that I could store the CD key in a way so that it would populate during the install so that I didn't have to type it in manually.

In x:\files\setup\setup.ini - find the [options] section and add in values as appropriate (you can also add company name, which is nice):

[Options]
; The option section is used for specifying individual Installer Properties.
USERNAME=User name
COMPANYNAME=Company name
PIDKEY=ABCDEFGHIJKLMNOPQRSTUVWXY


Please note the PIDKEY - which is the CD key is added with no dashes

Tuesday, February 5, 2008

Using Shadow Copies on Windows Server 2003

I have been vaguely aware that shadow copies are a means of recovering files without going to back up, but when I had a user request a file that she had deleted today, I decided to look into it. For Windows 2003 shares, you can recover deleted or saved/changed files BUT shadow copies has to be enabled first. In this particular case, shadow copies was not enabled. But here is how you do it:

--------

Shadow Copy is only available on Server 2003 machines and naturally you need NTFS (not FAT32). Configuration is easy, just click on the root of the any drive, Select a Volume, now press the Settings button. A crucial point is that Shadow Copy only works on network shares, and not on plain un-shared folders. So in passing, note that the number of shares for each volume. 'Best Practice' suggests that you place the 'Shadow' on a separate disk or at least on a separate partition. Personally, I would dedicate a disk to this service thereby improving performance. To change the drive, select the 'Details Button'.

Microsoft provide a schedule of two shadow copies a day, at 7:00 am and 12:00. You may wish to adjust these timings. When you select a schedule bear in mind that when you reach 64 shadows, the system starts over-writing. So make a calculation of how far back you would like to keep copies. My point is that if you go mad and schedule every hour, then you will start over writing within 3 days. Is that desirable? Would you want copies to be over-written so soon? I think not both on the grounds of load on the server and on how long you would want to retain previous versions.

--------

And then once it is enabled, here is how a user could retrieve files:

--------

To Recover a Deleted File

  • Drill down to the folder the file was deleted from.
  • Click in the list and then right-click the mouse to select Properties from the bottom of the menu. Select the Previous Versions tab from the Properties dialog box.
  • Select the version of folder that contains the file before it was deleted. Then click View. This will open the folder showing you the last saved version of the file. You can now select the file and drag and drop or cut and paste it from the folder to the target destination.

It is easier to recover a corrupt or overwritten file because you have something to select in the folder:

  • Right-click the bad file and click Properties.
  • Select Previous Versions as described above. To view the safe version, click View. To copy the old version to another location, simply click Copy and to replace the current version with the older version, simply click Restore.

Thursday, January 31, 2008

Embedding video into a Powerpoint

I already know how to embed an audio file into a Powerpoint (see previous blog entry) - but I had never needed to put video into a Powerpoint until today. I wasn't successful in making this work right - but it seems sound. Here are instructions for embedding a video into Powerpoint:

–Save video or video segment to your computer
–View > Toolbars > Control Toolbox
–Click on More Controls (hammer and wrench icon)
–Scroll down to Windows Media Player
–Draw a box that will become the image below
–Right click on the media player > Select properties
–Click on the empty cell next to “Custom”
–Browse for your video > Click OK
–In slideshow mode, you will be able to play the video embedded with controls like rewind, fast forward, sound, etc.
–You can also right click to open more menu controls, like View > Full Screen

Thursday, January 24, 2008

Outlook not opening with "the operation failed due to an installation problem"

Interesting issue today . . .

I had a user who logged into a Win XP computer (with Office XP and Outlook 2003). When the user logged in and opened Outlook, he got this:







The weird thing is that all users (I tried several others, all local administrators) got this same error. But I know that I set up a user on Outlook about 2 months earlier. When looking in the application event log, I saw this:























After some research, it turned out that I had to add a DWord key of UserData with a hex value of 1 in HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook. So it looked like this:







And then it worked. I feel like I'm going to have to keep creating this key for all users in the future. Perhaps, I should uninstall and reinstall - but not today.