TLDR – If you are not interested in how the PowerShell script works and just want to jump straight to the solution see the PowerShell script below; just be aware that the script only works when moving a VM to another vNET in the same subscription. To move a VM to a vNET in another subscription you need to follow a different process which will be documented in a future blog post; let me know in the comments if you’d like to see this happen. Moving an Azure VM to another vNET isn’t easy You’d think that since VMs move around a lot on networks that moving an Azure VM from one vNET to another in would be a simple task… it is not. In fact, Microsoft’s official view on this approach is that they do not support it – so this means you are left to figure it out for yourself.
This article specifically address a problem I found when trying to disable archiving on specific folders in Exchange by following Prevent Notes, Calendar and Tasks from getting archived by using EWS script. When running the script I would get the error The UserId in the folder permission at index [xx] is invalid. The rest of this article will assume you have read the linked post and understand it. The Cause The script works by downloading the settings of a user's calendar and adding a "no archive" personal tag to it, it then syncs these changes back to the online version of the folder. Where the problems starts is with the download of the folder; it doesn't just download the folder name, it downloads delegate permissions as well. In my case it wasn't downloading these permissions correctly so I had some blank entries (more on that later). After adding the archive tag it then tries to save the folder settings including the blank permissions resulting in the above error. The fix The above script downloads the user's calendar by calling the bind method on line 50. The default bind command downloads permissions as well. All we need to do is exclude them from
Backup to URL: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel
When performing an SQL backup using the feature “backup to URL” in, you receive the error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel or Backup to url received an exception from the remote endpoint Essentially what this error is saying, is that the certificate being used is not trusted.
Most of you reading this will already know what DNS Scavenging is. For those of you that don’t it is a feature of Windows DNS servers which allows you to automate the deletion (scavenge) of outdated DNS resource records. It sounds simple enough and it is once you decipher Microsoft’s cryptic descriptions, but to the uninitiated it is just plain confusing and often leads to unpredictable results. This article will attempt to simplify how DNS scavenging works. Enabling DNS Scavenging on Zones The first thing we need to do is enable Scavenging. This is done separately for each DNS zone.
This article is specific to Windows 7 but similar errors occur on all versions of windows. NOTE: You will need your Windows 7 DVD or a USB with the recovery console installed. IF USING A USB STICK MAKE SURE IT IS PLUGGED INTO A USB 2 SLOT, USB 3 IS NOT SUPPORTED; It will error with ‘failure when attempting to copy boot file’. After rebooting your computer you receive the following error: Windows Boot Manager Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1.insert windos cd and run a repair your computer option. File: /boot/bcd Status: 0xc000000f Info: an error occurred while attempting to read the boot configuration data. You may receive a similar error which lists the error code as 0xc0000034 or missing file: windows\system32\winload.exe instead. You may also receive further errors after trying to repair the bcd store using bootrec and bcdedit as follows. The requested system device cannot be found. The “Windows Boot Configuration Data File is Missing Required Information
You receive the error "A required CD/DVD device driver is missing" when installing Windows 7 or Windows 2008/R2 from a USB device. Furthermore if you browse to install drivers you will see that your CD/DVD drive is actually installed successfully. You are using a USB 3 Port The error is very misleading; the problem is not that the CD/DVD device drivers are missing, it is that USB 3 drivers are missing. Most likely you have plugged your USB drive into a USB 3 port but the problem here is that Windows 7/2008/R2 doesn't ship with USB 3 support. The solution is very simple; just plug your USB drive into a USB 2 port and start the install again. Why does this happen? The initial boot up will work fine but once Windows starts installing drivers it will fail for the USB 3 hardware. At this point the installation can no longer see the USB pen resulting in the error. By booting up on a USB 2 port Windows has the required drivers to continue the installation successfully. As for the "A required CD/DVD device driver is missing" error I can only guess this is because the install expects to be
VPN Passthrough is a feature of routers which allows computers on a private network to establish outbound VPNs unhindered. VPN passthrough has nothing to do with inbound VPNs, only outbound ones. The term comes from allowing the VPN traffic to “passthrough” the router. NO ports need opening to enable VPN passthrough, it will automatically work. There are different types of VPNs but the most dominant ones are PPTP VPNs and IPsec VPNs. When a router states it supports VPN passthrough it actually means it supports both these types of VPNs. To be exact VPN passthrough is just the combination of PPTP passthrough and IPsec passthrough. This is important as you will see next because PPTP passthrough is handled differently to IPsec Passthrough.
This article continues on from where Types of NAT left off. A symmetric NAT applies restrictions exactly the same way as a port restricted cone NAT but handles the NAT translation differently. All types of NAT discussed so far don’t change the source port when NATing connections. For example when a client accesses the Internet using IP 192.168.0.1 and source port 56723 NAT changes the source IP to say 18.104.22.168 but keeps the port number the same; this is known as port preservation.
All types of NAT fall into two categories; Static NAT and Dynamic NAT. Static NAT is where administrators manually create and maintain the NAT mappings and is usually associated with inbound types of NAT. Dynamic NAT is where the router creates and maintains mappings automatically on demand and is usually associated with outbound types of NAT.
Welcome to the final part in a 3 part series of articles about routers and routing . Previously I wrote about how routers work and the routing table in parts 1 and 2 respectively. I am now going to talk about IP routing and how you can manipulate routes to “direct” traffic.