Word showing {hyperlink "mailto:"} in front of email addresses

Situation:
all email address are showing up with {hyperlink "mailto:email@address.com"} in front of them

Solution:
alt+F9

Mac delete key doesn't work through logmein

Situation:
Mac laptop using logmein to connect to a PC

Problem:
Using Outlook on the PC, unable to delete emails by pressing the delete key on the Mac.  It just opens the Deleted Items in outlook.

Solution:
Press fn+delete key to delete the items through logmein.

Public Folders, Exchange 2013

Are a massive pain in the ass...

So you have the main mailbox, assigned the Primary Hierarchy, and all mailboxes beyond that are assigned the Secondary Hierarchy.
If a folder resides in anything but the Primary Hierarchy, you will NOT be able to add subfolders to it through Outlook.
You'll get this window:

The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action.

You'll still be able to add folders through the EAC, but this is a massive administrative pain if your users are adding subfolders all the time.
You will be able to move data like emails and tasks to it if its in a Secondary Hierarchy though.

If you have a folder tree like this:
Root public folder
                    ∟Team folder
                                          ∟ Folder for Stuff
                                          ∟ Folder for Stuff
                                          ∟ Folder for Stuff

That continues on and on for different root public folders, this is how you have to have them assigned on the back end:
Root public folder(primary hierarchy)
                    ∟Team folder (primary hierarchy)
                                          ∟ Folder for Stuff (secondary hierarchy)
                                          ∟ Folder for Stuff (secondary hierarchy)
                                          ∟ Folder for Stuff (secondary hierarchy)

This way, you're moving the actual data to another PF-Mailbox and allowing the Primary space to create other useable folders through outlook.
In the Folder for Stuff, you'll be able to add emails, tasks, etc, just not subfolders.

If you've migrated from a previous version of exchange and didn't map out your public folders like this prior to the move, here are some powershell scripts you'll need.  You'll need to be in the exchange shell, running as admin and logged in with a user that has exchange administration rights.

I'd just CD to the location of scripts since you'll be running a number of scripts.  The scripts are located in program files\Microsoft\exchange server\

so you'll need:
.\move-publicfolderbranch.ps1
This script moves the folder you select along with everything underneath it.  If you're moving a large folder, it will lock down all public folders until its done.
FolderRoot:
the location of the folder, if its a root folder, just type its name, if its not, type \home folder\sub folder\sub folder\etc until you get to the folder you're going to move.  If you use the EAC to find the public folder, drill down to as far as you need and you can copy the path/paste it into powershell with a right click.

TargetPublicFolderMailbox:
The pf-mailbox you're moving to (the secondary hierarchy folder)

To see the statistics:
get-publicfoldermoverequeststatistics -identity \publicfoldermove

Before you move on to the next folder move you have to remove the finished job (there might be a better way to go about this, but I'm new to powershell/coding in general)
remove-publicfoldermoverequest -identity \publicfoldermove

If you only want to move the root folder:
new-publicfoldermoverequest

You'll be able to select the folders you want to move with this command.

Sorry, Word Web App ran into a problem opening this document.

I've been working on documents on one drive pretty frequently.  I use the free onedrive account and all the word documents I use there were created in one drive, not uploaded.
Here's the problem, 1 document comes up with this error:

Sorry, Word Web App ran into a problem opening this document.  To view this document please open it in Microsoft Word.

Which I was able to do, so my data wasn't lost.  But I wanted to open it in browser so I could continue working on that file.

I was able to open up every other word document I created in one drive just fine.  This was happening in Chrome, Firefox and IE on two different computers.  Since downloading it worked, I know my data is still there and wasn't panicking too bad.

What I ended up doing to fix it was to create a share to the document with edit privileges, I copied that link and logged out of one drive.  Opened up the document and edited it, waited for the save to complete and closed out.  Logged back into OneDrive, and the document worked again.

System file checker found some corrupt files, but couldn’t fix them.

What should I do next?

Run:

dism.exe /online /cleanup-image /restorehealth 

Once that is done, run sfc/ scannow again and it should come up clean.

This works on Windows Server 2012, Windows 8 and Windows 10.

Adding groups to public folders powershell Exchange 2013

When I went through the Exchange Admin Center, I was only able to add user mailboxes to public folders, I wasn't able to add security groups.
After a quick bit of searching I found this script that let me add the group:
Add-PublicFolderClientPermission -Identity \PublicFolderName -AccessRights publishingeditor -user GroupName

Change PublicFolderName to the name of the public folder and change GroupName to the name of the group you want to have access to the public folder.

Go here to run the script:

Red X in outlook, already went through all the standard fixes...

Environment:
Windows 7
Outlook 2007


So you have these in Outlook:

The good old "can't see shit" red x.

You've probably gone through the Trust Center, to make sure "Don't download pictures automatically in HTML email messages..." box is UNCHECKED.

You've probably already opened a new message, clicked the office icon and gone to editor options>Advanced and made sure Show picture placeholders is unchecked.

You may have even gone to the registry and made sure the Secure Temp folder is both A. not full, and B. has the correct path.  (By the way, that key in W7/Outlook 2007 is: HKCU>Software>Microsoft>Office>12.0>Outlook>Security)

Have you check IE LAN settings to make sure Auto Detect is checked?  Stupid right?  I checked that too...  none of this did anything for me.

Have you read how Outlook doesn't handle https images correctly, resulting in red x's?  I read that too.  If you've done all this, you probably read the same forum article I did.  And the fix that finally worked was nestled toward the end.

!!!!!!!!!THE FIX!!!!!!!!!

What it ended up being was an IE setting.
Under Security, remove the checkmark in Do not save encrypted pages to disk

Thank you Mr. dajonline.  You're a life saver.

https://social.technet.microsoft.com/Forums/office/en-US/c8e7852c-6d0b-47e6-bc59-172464feb1ac/outlook-2007-blocked-images-red-x-for-https-links?forum=exchangesvrclientslegacy

DL380 g4 no video

Situation:
A previously working DL380
Plan to add drives to raid, currently raid is 3 drives.

Added drives, no boot.
Drives spin up, green lights on everything, eventually it appears to boot to the previous raid drives.  New drives have no lights, old drives have green.  No video.
No POST beeps.
Looked online, reseated the PCI riser, no change.
Added PCI video card. nothing.

Looked for lose connections, nothing.
took it out of the rack and sat it on a desk and took another look inside.  One of the memory modules was lose on the corner closest to the faceplate so I couldn't see this when it was in the rack, the fans blocked it.
It wasn't popped out much.  The hold down clip was undone slightly.
I don't remember touching the memory, but I must have.

So if your DL380 looks like its working fine but you have no video.  Check memory.

remotely restart a windows 7 computer, or maybe any windows OS

cmd > type: shutdown -i
Add the computer you want to restart
complete the rest of the form and restart.
(I also use this when I'm in remote desktop and need to reboot the computer I'm on.)

Taking down old DNS server ends the internet...

Situation:
Moving from 2003 to 2012 servers.
Multiple DCs running DNS
Shut down the last 2003 DC, all DNS fails.

Final DC was running the proxy server.  Turned off service, internet still worked.
Turned off DNS, internet stops working.

Turns out the other DNS servers weren't relying on the root hints, they forwarding traffic to one server that no longer exists, along with the last 2003 DC running DNS.

To view this, go to your Fowarders, DNS Manager>Click the server under DNS>Forwarders tab.  Similar to how you get to your root hints (http://randomcomputerjunkbyalex.blogspot.com/2013/05/updating-root-hints-on-dns-server.html)
Edit and remove old servers from here.

Note:  I had the checkmark in Use Root hints if no forwarders are available, but it still didn't use the root hints when the old 2003 server was offline.  DNS just stopped working.

Well, if I hope this helps someone out there.  I don't want to believe I'm THAT bad at computering.

Added computer to domain, doesn't show up in Active Directory

I recently had a computer crash.  So I reloaded it, named it the same thing and added it to the Domain.
I made sure to delete the previous entry before joining the domain.
The computer asked for domain credentials, and successfully added itself.
So I rebooted and I was able to log in with domain accounts.

However....

There's always a however...

The computer didn't show up in Active Directory Computers.
It didn't show up anywhere in AD.

I went back to the computer, removed it from the domain and added again.
Standard procedure.  Says welcome to the domain and requires a restart.  I oblige.

Check AD, still not there...

I thought I'd change the name, didn't work because the computer account wasn't found...

So here is how I got it to work:
Removed the computer from the domain.
Reboot.
Renamed computer.
Reboot.
Joined domain.
Reboot.
Verified account in AD.
Changed name on computer.
Reboot.
Verified account in AD, it was now the name I wanted to use.

All done.

Stupid PITA.