I have moved all existing content to my new self-hosted blog: thenetworkstack.com
This site will no longer be updated, so please go to thenetworkstack.com for updates and new content!
-Daniel
I have moved all existing content to my new self-hosted blog: thenetworkstack.com
This site will no longer be updated, so please go to thenetworkstack.com for updates and new content!
-Daniel
Our 2012R2 DC’s do DHCP and DNS for our environment, but I found that our client’s DNS addresses were frequently incorrect, even though DHCP is supposed to update DNS with the correct entry. Found this blog post that solved our problems:
Note: If you are unsure about running the dnscmd shown in the blog post, I found the commands to verify the setting before you change it, and how to revert:
Show current state:
dnscmd /info /OpenACLOnProxyUpdates
Desired state:
dnscmd /config /OpenAclOnProxyUpdates 0
Revert to default:
dnscmd /config /OpenAclOnProxyUpdates 1
After a power outage, we powered on our VMware infrastructure, and as we went through the process, we quickly realized that vCenter was not coming back online. vCenter was not reachable via icmp or http/https. Logging into the ESXi console showed the VCSA booting very slowly, but eventually it booted up. Still no network connectivity. After enabling bash and doing an “ifconfig”, I noticed the eth0 interface was missing. The “ip link show” confirmed that the VM did not recognize any eth0 devices, but it did pick up an eth1 device. For some reason, the vnic mac address had changed, and vCenter added the nic as a new device. To resolve this:
This process will clear the static mac association with the previous eth0 nic, and will allow VCSA to boot up with the new nic/mac address as eth0.
Reference: http://www.vmwarebits.com/content/how-fix-vcenter-appliance-no-networking-problem
Enable SCP to easily transfer files to devices (especially if you are behind a NAT):
http://www.ccierants.com/2011/06/great-way-to-copy-files-on-cisco.html
Example: pscp -scp ios-filename.bin admin@routerIPaddress:ios-filename.bin
Implemented WebEx with ADFS SSO (Windows 2012R2) successfully, and found these articles helpful:
Initial Setup:
https://cisco-support.webex.com/guest/articles/en_US/Usability_FAQs/WBX63102/myr=false
Those guides do not go over configuring sign-out. This can be accomplished with the WSFederation sign-out URL documented here:
And configuring your ADFS server with:
1. Go to AD FS Manager – Trust Relationships – Relying Party Trusts – <your party trust> properties
2. Under the Endpoints tab, click Add SAML…
3. Endpoint Type = SAML Logout, Binding = POST, Trusted URL = https://myadfsserver.domainname.com/adfs/ls/?wa=wsignout1.0
Connecting to Office 365 via Powershell for the first time? Here are the steps to get started:
UPDATE: Here is an awesome project on github that is a Office 365 Powershell GUI: https://github.com/bwya77/O365-Administration-Center
Microsoft References:
https://technet.microsoft.com/en-ca/library/jj151815.aspx#bkmk_installmodule
https://technet.microsoft.com/en-us/library/jj984289(v=exchg.160).aspx
If you use Office 365 and DirSync, a user’s primary email address can end up being username@domain.onmicrosoft.com if not setup correctly. To identify all users setup this way, connect to Office 365 powershell and run this command:
Get-mailbox -ResultSize unlimited | Select-Object primarysmtpaddress | ? {$_ -clike “*onmicrosoft*”}
If you need to change the postgres external database for CUCM, there a few steps to follow:
This blog post helped figure out the process: http://collabtechnotes.blogspot.com/2015/07/postgre-sql-cisco-xcp-message-archiver.html