We are about to enable scavenging for DNS here at work and needed to get a list of DNS entries that were set to not scavenge. I did it like this:
The text file you get at the end has the entries that don’t age. That’s it!
Note: I had a little help from Marcus on this. He has a post similar here.
I am probably the only person on the planet doing things this way, but I want to document this anyway.
In the scom web console, I am publishing views for various bits of the business. Then I am using this procedure mentioned here. This is not perfect because you cannot save the way you want a performance view to look (which counters are checked) but it at least is a start. (Hello Microsoft! Please fix!) In order for the whole thing to be easily memorable, I create a url like http://weberrors, and this error contains… the website errors.
How I am doing this is pretty easy.
This is a pretty simple thing and it makes navigating to specific spots in the SCOM UI much easier.
Note: If you do not check the box for “redirect all requests to exact destination” then when IIS redirects it will add an extra slash “/” to your URL. Scom does not like this! You will get an error:
All you have to do is what’s in step #7 above. That’ll make the redirects do their thing properly.
I have had my Jeep for a few months now but just now got it to the point where it’s not stock and worth at least speaking about and showing pics of and whatnot. My cousin is Graham of Rough Customs in Acworth, GA (used to be in Cartersville) and he did all the fab work for me. The setup is all his design, using SOA up front so it would ride good and flex while staying more conventional in the back because of axle wrap issues. This is my first jeep and my first real off-road vehicle other than my mostly stock 98 F150. It’s been out on what Graham called “medium” trails and it does real nice. The tires stay on the ground and even open on both ends it’s made it up everything I have tried with very little drama, so I’m a very happy camper right now.
Here are the specs
Front
Rear
Future
Here’s a link to some pictures I took during the build and afterwards.
And just for fun, here’s some video of Graham messing around in his CJ.
This is a little blurb I use almost everywhere for almost everything that will log all sorts of useful info about a .net app in the application log. It will grab unhandled exceptions as well as application lifetime events (app pool or domain restarts, etc.) This is a really good one to use when your devs won’t add this to the code themselves! It will work (or has for me) straight up in any .net code. All you do is place this in the web.config.
<healthMonitoring enabled="true">
<eventMappings>
<clear />
<!– Log ALL error events –>
<add name="All Errors" type="System.Web.Management.WebBaseErrorEvent" startEventCode="0" endEventCode="2147483647" />
<!– Log application startup/shutdown events –>
<add name="Application Lifetime Events" type="System.Web.Management.WebApplicationLifetimeEvent" startEventCode="0" endEventCode="2147483647"/>
</eventMappings>
<rules>
<clear />
<add name="Application Events" eventName="Application Lifetime Events" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" />
<add name="All Errors Default" eventName="All Errors" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:00:00" />
</rules>
</healthMonitoring>
This is harder than it should be. Here are my notes on doing this.
1. On cert server go here: http://blah/certsrv/
2. request cert. choose type other and paste in the below OID
3. OID = 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2
4. Make sure to check key exportable. Make sure to use FQDN of server for name and common name.
5. Open up server mgt for certificate manager and approve.
6. Go back to website, install the cert.
7. Mmc, certificates for personal. Export the cert. make private key exportable.
8. Copy cert to client server.
9. On server do mmc for client, import cert, mark as exportable.
10. Run momcertimport on client, choose cert.
11. Restart system center manager service on client.
12. Wait a min and go to mom console, administration, pending management. Approve it.
13. Done!
In case you weren’t aware, for SCOM to work against a non domain machine, all manner of certificates is required between the RMS and the agents in order for this to work. Not only is it required, but you have to use the fairly archaic tools provided with certificates, oh, and you will need your own certificate authority too. This is such a complete and utter #FAIL that I don’t really know where to start. Mainly my issue is that it doesn’t need to be this hard.. if someone wants to see the CPU time on my webserver, then by all means, hack in, but damn if I care enough to go through this level of work for it. And that brings me to my second issue, the shit just doesn’t work. Sure you could say this is a “rush it out the door” kinda thing, but this happened back in 2007 and there have been plenty of releases including an R2 version, yet still this useless and archaic process is still in place.
So in short, the SCOM guys failed by over-complicating something that isn’t needed, and then making it 10 times more difficult than necessary. FAIL.
I was trying to use this and did not realize it was not installed. In order to get it you need to install the support tools. They are on the windows server 2003 cd, or can be downloaded here.
I have a Highpoint RockerRaid2310 in my server at the house. For some time I have had an issue with the “HighPoint RAID Management Service”, which runs an .exe called “hptsvr.exe”, which then runs “drvinst32.exe”, taking up a lot of cpu time. In my case the server was a quad core and it took 25% of the total CPU. Everything would work just fine, but this bothered me for a lot of reasons, so I would leave the service set to manual unless I needed to run the card’s management software. In that case I would start the service, do the management, then kill the offending .exe. Life went on.
Recently I decided I wanted to use more of the features of this card, so I went looking for a fix. There were several random internet posts about the problem but no one had a fix for it. Contacting HighPoint support seemed like the obvious thing to do, so that’s what I did, and they proved helpful.
In my case I was running the older management software, which was version 3.14.5. This was the latest version of it. I was also already running the latest version of the firmware (2.5) and windows driver (2.3). At the advice of HighPoint’s support, I switched to the web management software which is version 1.5.3. I did have an issue with the new software installing itself in the same directory as the old software, which broke my ability to uninstall the old stuff, so my recommendation if you do this is to uninstall the old version first. This has left an uninstall for the old version in add/remove and for now I’m just going to leave it, but that’s not hard to clean up.
So now life is good, I can schedule verify tasks, get emailed if a disk fails, all that good stuff. Basically, things are working as they should.
Applying update to a clustered RMS
If the install fails and you need to run it again, this is where it installs it (on an x64 system)
C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\
If the install fails and you need to run it again, this is where it installs it (on a 32bit system)
C:\Program Files\System Center 2007 R2 Hotfix Utility\
Powered by WordPress