We are currently in the process of stripping down mailbox permissions for our users. I used the following procedure to export the info into a ".csv" file for easy viewing.

• Log onto the domain administrator account on your Exchange server.
• Open the "Exchange Management Shell"
• Navigate to the desktop with the "cd" command.
• Type in the following command, replacing user.name and filename with the user you would like to audit.
  
  "Get-Mailbox | Get-MailboxPermission -User USER.NAME | Export_Csv -NoTypeInformation FILENAME.csv"
  

Hello folks! This is my first of many IT blog posts, mainly to help me remember stuff, but you may glean some useful stuff off of it too.

At my work, we are currently rolling out a new Lync phone system, and this quirk started showing up with several users. This is what I did to solve it...

First! Make sure the user hasn't actually disabled their picture on their Lync client. You don't want to waste time on a more complex fix that will essentially do nothing if they have their photo hidden.

In rare cases, the contact list may be corrupted because of an invalid character in an "out of office" message or because a lingering deprovisioned contact exists. To resolve this problem, force a contact list update to make sure that your information is synchronized. To this, follow these steps:

1. Locate one of the following folders, depending on your operating system:
   • For Lync 2013:
     • Windows Server 2008 R2, Windows 7 and Windows 8: %localappdata%\Microsoft\Office\15.0\Lync\sip_<sign-in name>
   • For Lync 2010:
     • Windows Server 2008 R2, Windows 8, Windows 7, or Windows Vista: %localappdata%\Microsoft\Communicator\sip_<sign-in name>
     • Windows Server 2003, Windows XP: %userprofile%\Local Settings\Application Data \Microsoft\Communicator\sip_<sign-in name>
2. Delete the following files:
   • Galcontacts.db
   • galcontacts.db.idx
   • CoreContact.cache
   • ABS_<sign-in name>.cache
   • Mfugroup.cache
   • PersonalLISDB.cache
   • PresencePhoto.cache
3. Restart Lync, and then wait for 30 minutes for resynchronization to finish.

*When doing this, be conscious of the effect this may have on the users, especially while dealing with executable files.*

I was requested to delete a file by our developer, Jason the other day and had no way of finding out who was using the file(We use Terminal Services). I tried a forced deletion of the file. To do this, you will need to open the command prompt.

• Log into the terminal server where the file is located with administrator credentials.
• Click on the "Start" button and type in "cmd."
• The command prompt executable should appear. Click on it to run.
• Before going any further, you should find out where the file is located. Write down the full directory path.
• In the command prompt, enter "cd c:/full/directory/path/of/file"
• Type in "dir" and hit enter to confirm you are in the correct directory.
• To delete the file in use, type "del fileinuse.exe"
• The file will be forcefully deleted and disappear from the directory.

You can use the very nifty command line tool, PSEXEC to dump all of the ipconfig settings into a text file! You can download PSTOOLS (Including PSEXEC) here.

To do this, open up the command prompt by clicking "Start" then searching for "cmd."The command prompt icon will show as "cmd." Right-click it and run as administrator.In the command prompt, type in the following command...
"psexec \\* ipconfig /all > c:/output.txt"

PSEXEC will display a message telling you that it is enumerating the domain. This may take a while!

Once it has finished, a text file called output.txt will appear on the root of the C drive containing the ipconfig settings of every windows machine on the domain.