— pissing into the wind

Archive
Microsoft

Noticed IPv6 DHCP was broken on all my Windows 10 clients after I upgraded to the anniversary edition (1607).  Had to run a couple powershell commands to get them pulling addresses:

Wired:

Set-NetIPInterface ethernet -AddressFamily ipv6 -RouterDiscovery Enabled
Set-NetIPInterface ethernet -AddressFamily ipv6 -ManagedAddressConfiguration Enabled

Wireless:

Set-NetIPInterface wi-fi -AddressFamily ipv6 -RouterDiscovery Enabled
Set-NetIPInterface wi-fi -AddressFamily ipv6 -ManagedAddressConfiguration Enabled

That’s it!

Read More

I’ve been a longtime fan of Windows Live Writer for many years.  Alas, it has been unsupported for many moons and I haven’t been able to get it working with SSL.  The good news is that Microsoft decided to release WLW to the open source community.  The even better news is that someone has forked the code and taken up the mantle.  If you’re an existing Windows Live Writer, I suggest you give Open Live Writer a try.  The setup and user interface will be familiar and things seem to work overall.

Read More

After I installed Exchange 2013 and tried to access either OWA or ECP on it, I kept getting Error 500.  Looking at the httpproxy logs, I saw this: The unhandled exception was: System.Security.Cryptography.CryptographicException: Invalid provider type specified.

Turns out Exchange doesn’t like the key provider, Microsoft Software Key Storage Provider, so you have to reissue a cert using Microsoft RSA SChannel Cryptographic Provider as the provider.

I did this by going through the web cert enrollment and using the Web Server template.  Then I assigned the new certificate to the SSL sites in IIS.

The solution is over here.

Read More

it never fails, it never fails… or rather it always seems to fail:  exchange service packs or rollups.  I’ve had to fix quote a few at work and in my home lab.  one thing that I’ve come across multiple times for exchange 2010 is to run a powershell script that automagically fixes the issue.  this post has it right:

Typical, i spend ages looking about with no joy but as soon as i post i find a solution!
For anyone else with the same issue;
"After you install update rollup 1,2 or 3 on an Exchange 2010 Client Access Server you often get a blank OWA page when browsing to the OWA page.
After installing the rollup updates you will receive something like the following URL;https://mail.msexchangeblog.nl/owa/auth/logon.aspx?url=https://mail.msexchangeblog.nl/owa/&reason=0 .
To fix this issue you must start updatecas.ps1 in the Exchange Management Shell. You can find the script in C:\Program Files\Microsoft\Exchange Server\V14\Bin . The script updatecas.ps1 will handle the OWA and ECP updates. The updatecas script comes with the update rollup."

That’s it.

Read More

So that servers get only one ipv6 address…

C:\Users\administrator.GUAMMIE>netsh int ipv6 sh int

Idx     Met         MTU          State                Name
—  ———-  ———-  ————  —————————
  1          50  4294967295  connected     Loopback Pseudo-Interface 1
10          50        1280  disconnected  isatap.{1C882B80-03D8-4F3C-B703-6A1DC1768F6B}
11          50        1280  disconnected  Teredo Tunneling Pseudo-Interface
14           5        1500  connected     Local Area Connection 4

C:\Users\administrator.GUAMMIE>netsh int ipv6 sh int 14

Interface Local Area Connection 4 Parameters
———————————————-
IfLuid                             : ethernet_9
IfIndex                            : 14
State                              : connected
Metric                             : 5
Link MTU                           : 1500 bytes
Reachable Time                     : 27000 ms
Base Reachable Time                : 30000 ms
Retransmission Interval            : 1000 ms
DAD Transmits                      : 1
Site Prefix Length                 : 64
Site Id                            : 1
Forwarding                         : disabled
Advertising                        : disabled
Neighbor Discovery                 : enabled
Neighbor Unreachability Detection  : enabled
Router Discovery                   : disabled
Managed Address Configuration      : disabled
Other Stateful Configuration       : disabled
Weak Host Sends                    : disabled
Weak Host Receives                 : disabled
Use Automatic Metric               : enabled
Ignore Default Routes              : disabled
Advertised Router Lifetime         : 1800 seconds
Advertise Default Route            : disabled
Current Hop Limit                  : 0
Force ARPND Wake up patterns       : disabled
Directed MAC Wake up patterns      : disabled

netsh interface ipv6 set interface 14 forwarding=disabled routerdiscovery=disabled managedaddress=disabled

Read More

Started a new job a few weeks ago and now that the new team is all done with training, we’re going through and trying to fix things we’re coming across.  One of the errors that showed up on every single domain controller is 8194 and has to do with Group Policy Registry happening every 5 minutes .  The fix for this is pretty simple.  Look up the ID of the GPO in the event log.  Navigate to c:\programdata\microsoft\group policy\history.  You may have to show hidden folder or system folders if they are not visible.  If you drill into the problem directory, you should come across a Registry.xml file that is 0Kb.  Rename the ID folder to <original name>_old.  The errors should stop.

It seems that for whatever reason or another, that policy gets corrupted and needs to be recreated.

Read More

for /L %x in (1,1,255) do @ping -n 1 192.168.0.%x -w 100 | find “Reply”

This works right in CLI

Read More

1) Add machine2 as an administrator to machine1

2) Create a batch file with the following 3 lines:

C:\Windows\System32\netsh.exe -r machine1 nps export filename=”c:\npsexport.xml” exportPSK=”YES”
c:\windows\system32\netsh.exe nps import filename=”c:\npsexport.xml”
del /F /Q c:\npsexport.xml

3) Create a scheduled task

Done.

Read More

So I’m in the mood to upgrade my virtual server.  Right now it’s running some Phenom II Quadcore with 8GB of RAM.  There are 2 320GB disks in a Raid 1 using the onboard nvdia controller.

The disk configuration was a big deciding factor when I was trying to choose between Hyper-V R2 or ESXi 4.x.  Simply put, ESXi doesn’t recognize the controller as anything more than a standard SATA controller, so RAID and thus ESXi were a no-go.

Microsoft’s built in management tools for Hyper-V never appealed to me.  I don’t feel like I can do enough to the host OS.  Plus, getting them to work in the first place is an ordeal itself.  See http://blogs.technet.com/b/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx.  Now that everything is up and running, I don’t want to touch it lest I break anything.  I hate this kind of feeling with systems and replace them with something more manageable ASAP.

I’m not sure how well Systems Center works for managing multiple Hyper-Vs in an enterprise, but vCenter works very well and it’s quite robust.  I feel like it is a very complete management solution for a virtual machine environment.  I digress though, this is just for home and only 1 machine.

Another thing that I don’t like is the lack of memory overcommit.  Hyper-V won’t let me provision more than 7 of the 8GB for the guest systems.  As I experiment and put in new systems, this is becoming a real hard limit and I’m pretty much stuck right now.

So, I’ve made the decision to do what it takes to get onto ESXi.  First thing I need to do is replace the RAID controller.  I picked up a Dell Perc 6i WITH battery (score!) off of eBay for cheap.  Almost all of the controllers do NOT come with brackets, so I had to purchase one from Mouser electronics.  My plan is go at least 2 1TB drives for OS and at least 2 2TB drives for a file server all a minimum of RAID1.  I might do something else if I can pick up more drives, but no 0.  To get this going, I need a 32-pin to 4 SATA cable.  One can be had from Dell or Amazon for about $20.

Once this is in, I’m going to have to P2V all the servers from Hyper-V hell using VMware Workstation on my desktop as purgatory before I bring up the ESXi host and then import them into VMware heaven.

I’m then going to up the memory on a couple of systems to see what performance is like when I overcommit.  If it’s acceptable, then I’ll be happy for about 5 minutes.  At some point, I’m going to pull all that RAM and add 4 4GB sticks to max out the system at 16GB of RAM anyway.

Right now I’m just waiting on the cables from Amazon and then I have to order hard drives from Newegg.  One other thing I’m worried about is heat.  The case I have does not have any cooling over the hard drives and I noticed the ones in place now are pretty hot.  That may be another cost that I’m eventually going to have to consider, but I’ll cross that bridge when I get to it.

Read More