DNS not routing to forwarder in Forward Lookup Zones

I recently had an instance where the server name contained dashes only.
I configured an lookup zone and A record like I do with many other sites, but this one wouldn't work.
Ping name-name couldn't be found.

After some Googling, I determined DNS was seeing the name as a single label name.
I also found out WINS used to handle situations like this (no running WINS server on my network)
But Microsoft offers a solution for server 2008 and above called GlobalNames

I will put the scripts I ran in Powershell here, at the bottom are the pages I pulled the information from, their pages contain GUI instructions.

dnscmd servername /config /Enableglobalnamessupport 1 (you will do this step on all servers running DNS, cool thing about powershell is you can do it all from this one prompt, just up arrow, change the server name and hit enter.)
dnscmd servername /ZoneAdd GlobalNames /DsPrimary /DP /forest

At this point you can go into your DNS manager GUI (Start>Admin tools>DNS) go to your Forward Lookup Zone and find GlobalNames.
Right Click
New Host (A or AAA)
Enter the name (it will show up name.globalnames)
Enter IP address (remove checkmark in create associated pointer (PTR) record)

done.

I had to flush dns (ipconfig /flushdns) and I reran the 'enableglobalnamessupport 1' on a couple servers running DNS after creating the A record.

Restart services the easy way and without end user interaction

Occasionally I've had to do a full ip release and renew to get things working again.  When I'm remoted in I've done the ipconfig /release and had to have the end use type in ipconfig /renew.

There's been a 'solution' to my 'problem' all along:

ipconfig /release && ipconfig /renew

This will release the IP and renew the IP once the previous command completes.

This will also work if you have to do something like restart a spooler
net stop spooler && net start spooler

Or any other services that you have to stop start rather than just restart.

WDS completes, no boot device on startup.

F1 to retry

You know the error screen.

Situation:
Dell Latitude e7440, solid state drive
Came with windows 8, used WDS to put vanilla W7.
W7 completes, but doesn't boot.

I went into BIOS, secure boot was disabled
UEFI was enabled, changed to legacy and it booted right up.

Also, with these e7440, I've been moving the SSD into the MSATA port.  I had an issue with one of the first e7440 that was losing the regular SATA connection, randomly.  I'd get the system and it would boot up, everything would be fine, I'd send it back to the user, it wouldn't work again.  The back panel is kind of flimsy, so I can only assume he was holding it toward the top, or the docking station was pressing against the cable causing the hard drive connection to come loose.

Move computers to groups in logmein central

Sounds simple right?  I was in Details view and for whatever reason I couldn't figure it out until I switched to List view.
I'm using Chrome to load the Logmein Central page.

Change to List view
Click the drop down by the computer you want to change and go to Properties
On this window you'll have a drop down for the groups you've created
Select the group and save

Moving a VMware machine from one physical machine to another.

First, SSH has to be enabled on each of the physical hosts.
on the VM host, hit F2 and log in.
Go to Troubleshooting Options.  I turned on both the ESXi shell and the SSH shell, then restarted management agents, I don't know if I had to do all that, but I did.
Once you've done that, go to your vSphere and go to the Configuration tab.
Click Security Profile under Software.
Click Properties under firewall, I put a check mark in SSH Client and SSH server.

This would be done on both physical servers.


I used Putty to connect to the server that housed the machine I wanted to move.  Once your connected, type:

scp -r /vmfs/volumes/(your datastore name)/(your VM host folder) root@ip.of.new.server:/vmfs/volumes/place/it/goes

It should then ask for the root password.  Those are not two separate commands, there's a space between (your VM host folder) and root, but it would all be on the same command.

SCP lets you move files, SCP -r lets you move directories, if you forget the R you'll get an error that its not a regular file.
I would also get "no such file or directory" the first couple of times I tried this, ESXi is case sensitive, so make sure you use proper case.

I also had issues finding out the path of my files.  To find out your path, go to your vSphere Client.
Click Configuration
Under Hardware, go to Storage
click on your datastore, this gave me the /vmfs/volumes/ part, the hex identifier can be replaced with the name you gave your datastore, this is located under identification.
You can right click the datastore, and go to Browse Datastore to see the folders that hold your virtual machines.


Also, in my environment I was only getting transfer rates of 4-5mbps.
This is on a gig network, with 10k SAS drives, transferring from a G7 to a G5 HP server.

**********
Also....

If you go have a big enough drive, you can copy the files to your computer, and then upload them to the other server.  This is the video that helped me.

https://www.youtube.com/watch?v=XSZdWQMynhw&index=4&list=PLe-uhdcSI8Z3FSPcGdUvnurCcGuW4vESm

*****************Update on transfer speed*******************
I was able to double the 4-5mbps by changing the raid of the target server.  I was running RAID 5, changed to RAID 10 and saw 9/10mbps,  So the limitation before was the Hard Drive speed, which makes sense and I should have known, but I guess I just took for granted.

Unable to update the IP address on Isatap interface isatap.

Environment:
ESXI 5.5
Windows Server 2012 R2

Error comes up when running DCdiag.

To clear this I went into Device Manager, show hidden devices, disabled and uninstalled the ISATAP connector.

Clean DCDIAG after that.

WDS capture, windows failed to start 0xc000000f

I'm trying to capture an image using WDS.

I went through the proper steps of creating a boot image and then a capture image.

The Boot image loads fine, the capture image results in this screen:

WDS is running on fully patched (as of 3/10/2015) server 2012 R2

After searching the internet and finding a number of people have this issue, some referring to KB2919355, I finally found a fix that worked.
(If you are wondering, no, removing KB2919355 and reinstalling WDS did not work for me.)

I used DISM to mount and unmount the capture image.  I created a "MountDir" folder on the same drive as the rest of the boot files.  In red are the variables for whatever you called your capture image.wim and wherever you want to mount it to.

C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Mounting image
[==========================100.0%==========================]
The operation completed successfully.

C:\>dism /unmount-wim /mountdir:C:\MountDir /commit

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
Image Index : 1
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.


And that's it.  Mount it, do nothing to it, unmount it saving 'changes' and viola.  You can now boot to the capture image.

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.