Wednesday, February 26, 2014

Fixed: Ubuntu 6.06 LTS on Windows 8.1 Hyper-V

Ubuntu 6.06 LTS will install and run on Windows 8.1 Hyper-V given the following caveats.
  • Use the Legacy Network Adapter.  The newer network adapter is not detected by the OS.
  • Disable Apic and ACPI for both the initial install and the running OS.
  • The boot splash screen looks like its hung.  It's not.
Installation Procedure:
Replace the VM default network adapter with a legacy network adapter.
Insert the CD and reset the machine.



Press F6 for additional installation options.
The screen looks like this.

Remove the -- from the boot options and add " noapic acpi=off".

Press Enter.  The splash screen will appear to hang.  Be patient.  This will clear in approximately 2 minutes. Be patient. 


When it boots, Install as normal.

 When prompted, reboot.

Your VM will fail with a Kernel panic on the first boot.  That is expected.

 To boot to the OS, we have to change the boot options like we did for the initial install.

Reset the VM.
Press Escape for the grub menu

Press E to Edit the Boot Options



Scroll down  to the kernel line and press E to edit it.


Add noapic acpi=off  to the end of the line and press enter to return to the grub menu


Press b to boot. Yeah! A login screen.  Now login.


Almost done.  The last thing to do is edit the boot options permanently so you don't have to do that every time.

Open a terminal prompt by selecting Applications -> Accessories -> Terminal
Then Type  sudo nano /boot/grub/menu.lst


Scroll down and find the line that starts with #kopts=

To the end of this line add noapic acpi=off
Press Ctrl-X to exit and Y to save.
Type sudo update-grub


That's it.  Now your bootloader options are set properly in the menu.lst file.  If you reboot, it should boot straight to a login prompt with no magic required.

Magic!

You might be asking "Why on earth would I want to run an 8 year old unmaintained operating system?"  I have a customer question regarding Samba 3.0 and AD interoperability.  This VM gets me to the right Samba era to test my assumptions.  Viola!

(I won't mention my Windows NT 4 VMs either!)

Tuesday, February 25, 2014

Fixed: DHCP Server won't start with error "The DHCP/BINL service is not authorized in the directory service domain "2A040000" "

In my Lab I've been having some trouble with the DHCP server.  Today I finally got around to working on it.

On my freshly installed DHCP server I got the following 3 events.

DHCP Event ID 1004
Event ID: 1004
The DHCP service failed to initialize the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.

Event ID: 1018
The DHCP service failed to restore the database. The following error occurred:
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.



DCHP Event ID 1008

Event ID: 1008
The DHCP service is shutting down due to the following error:
The DHCP/BINL service is not authorized in the directory service domain "2A040000" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain "2A040000" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain "2A040000" (Server IP Address The DHCP/BINL service is not authorized in the directory service domain "%2" (Server IP Address %1)
)
)
)




It's worth mentioning here that my AD domain is contoso.com, NOT 2A040000.  That error looks like an unhanded exception that is falling through to the wrong error message.  The only explanation I could come up with for this was that my DHCP database was corrupt.  I tried removing and reinstalling the DHCP Role, but that did not fix it.  My solution was to delete the DHCP database and recreate it as follows.

Warning: This will lose information about all of your active scopes, options, and leases.

  1. Stop the DHCP Service.
  2. Use the DHCP MMC to de-authorize the dhcp server.
  3. Move the contents of  c:\windows\system32\dhcp to a temporary folder.
  4. Start the DHCP Service.
  5. Authorize the DHCP Service in the DHCP MMC.
  6. Create the DHCP scopes.
Cross-posted on the Microsoft forums here.

Monday, February 24, 2014

So then I cooked: Italian Breaded Pork Chops

Tonight I made Italian Breaded Pork Chops from AllRecipes.com.  It was ok.

A couple of notes:
The instructions are based on thick pork chops.  I had thin slices of tenderloin so the cooking time went down significantly.
The recipe makes a lot of breading.  You can half it and still have plenty for four.
Add salt to either the breading or the finished meal.
Dip the pork in flour, then egg, then breadcrumbs.  The flour helps it stick more.

I'm sorry I'm not posting more, it's been crazy busy.

Friday, February 21, 2014

Reading: Influx

I'm quickly becoming a huge fan of Daniel Suarez's books.  A friend down in Atlanta recommended Daemon.  I got that one and I just couldn't put it down.  The sequel, Freedom, was great too.

A couple of weeks ago I picked up Kill Decision in Booked Solid down in Milwaukee.  I didn't make the connection that it was from the same guy until I finished it and looked to the about the author to see what else he'd written.  Wow!

Yesterday was my lucky day!  His newest book, Influx, just came out!  Yeah!  (This will be a great read for the plane ride home.)

(Full Disclosure: that is an affiliate link to Amazon.)


Thursday, February 20, 2014

Quickie: How to change the Administrator Password on an SCCM Windows 7 deployment

Today I needed to update the default administrator password in an SCCM Windows 7 Operating system deployment task sequence.  It took a bit to find it.

To change this, edit the task sequence.  Expand PostInstall -> Apply Windows Settings -> Enable the account and specify the local administrator password.

Note: The best practice is to set a random password and disable the account during the OSD.  Then you can do what you want with the account via GPO after it joins the domain.  This customer isn't following that for this particular sequence because it is the reference image.  They want to log in and check the reference image before pulling the WIM file.

Tuesday, February 18, 2014

Making an MSI package for Access 97 for Windows 7

Today I had my first experience with Flexara's AdminStudio.  I used the AdminStudio repackager to make a custom .MSI for Access 97.  This software lets you capture a before and after snapshot of a machine and turn the differences into an MSI package.  SWEET!

My current client has a huge installed base of Access 97 "applications" that run their business.  Unfortunately Access 97 is junkyard ancient and very not supported.  It won't even install out of the box on vanilla Windows 7.  I was able to find instructions on getting it installed on Win7 at http://social.technet.microsoft.com/Forums/windows/en-US/6b98381b-44ff-43d4-a9b1-1fb00023d3d5/install-access-97-and-office-2007-on-windows-7?forum=w7itproappcompat.

I had to add one extra bit to those instructions.  Setup.Exe was failing the install with a does not meet minimum system requirements error.  I set the Windows 2000 compatibility flag on Setup.exe to get the installer to run.  I did not have to set any compatibility options on the completed MSI.

That's great, Unfortunately a 10 step install process isn't going to work in an enterprise.  It's just not feasible to do that hundreds of times.  The right solution is to recode the apps into modern software.
The right-now solution is to repackage the software into a .MSI.  AdminStudio to the rescue.

First I installed SQL and AdminStudio on a Windows 2008 server.  I'm using the demo version of AdminStudio, as it's mind numbingly expensive.  

I spun up a clean Windows 7 SP1 PC and mapped a network drive over to the AdminStudio Box.  Then I captured the pre-install snapshot.  Next came the laborious Access 97 install.  Then SR1.  Then SP2 and the font stuff. Finally I was able to capture a post-install snapshot.  This rolled up all of the file and registry changes for Access 97 into a AdminStudio Package.  After I switched back to the server with AdminStudio installed I was able to select what components needed to go in the .MSI, and what could be left out.  A half-dozen build and test cycles later, it works!

Here are a few screenshots. 






I'm really impressed with this software.  It does everything I needed it to do, with a usable online help system.  Five Stars.  (-1 for high cost, +1 for fully functional 21 day demo.)

Last but not least, welcome back to my old friend Clippy!  Long time no see.

Author Trivia:  When this software was released I was working in a Truck repair shop changing tires.  Some days I miss it.

Note:  The customer is buying AdminStudio for internal use.  I'm not sticking them with a time-bombed demo.  That would be evil.

Quickie: Human resistant passwords

Today a random conversation popped up.  How do you make human being resistant passwords?  i.e. passwords that are difficult for a human being to read to another human being?  Length is an obvious answer, as a crushingly long password can exceed human memory buffers.  What else?  How about high ASCII or Unicode characters?

I arbitrarily restricted myself to a US keyboard and 15 character length.  using Here's what I came up with.

Dyslexia Passwords: 
  nnmnnvwvvwvwvuu

Font Abuse Passwords:
  |l1l1|1!l|1!ll

"Evil" Passwords:
  ;:.::;;:.::.:;
  "'`"`"'`'''``"

That last one is my favorite.  You can write it up on a dry erase board and it looks like a bunch of commas.  Evil.