Skip to main content

2008 R2 troubles continued, but solved

Once I got the disk portion working, it failed at the 'Copying files' part, got to between 15 and 40%, then gave an error (0x80070750 - files missing). I burned another DVD at 4x speed, same error. I re-downloaded the ISO, checked the SHA-1 hash, and burned another DVD at 4x speed. Same error. I made one of my USB sticks an install disc (http://myitforum.com/cs2/blogs/bbird/archive/2008/10/01/making-a-usb-stick-bootable-for-vista-or-server-2008.aspx , an excellent post, btw), and STILL the same error.

At this point I was pretty frustrated. There was no way it was install media-related...so back to the basics. I pulled all the expansion cards and did more googling. I came up with someone mentioning that over 4GB of RAM caused their Win7 install to fail. Win7 and 2008 R2 are similar, so I pulled 3 of the 6GB RAM I had installed (2x2,2x1). Bingo!! Installed 100% from there.

Pretty dumb problem...especially since it's an x64-only OS.

The hardware I'm using is most likely the culprit: Asus P5E-VM HDMI with the 0604 BIOS

At any rate...all good now.

Comments

  1. Same problem was when I was trying to install the SBS 2011 on a 8GB system with ASUS P5Q.
    Removing my extra 4GB solved it after several hours of trying.....
    Thanks!!!

    ReplyDelete
  2. I have the same problem installing SBS2011 as a virtual machine under Hyper-V 2008R2 SP1 or under VmWare ESX1 4.1. Any solutions ?

    ReplyDelete

Post a Comment

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…