Found this on Quora
People always want what they can’t have.
Here are three reasons why this is so:
1. Heightened attention: When something is hard to get (or forbidden) you immediately pay more attention to it. Notice that when you are on a restricted diet, you sometimes get too focused on what you “can’t” eat. This heightened attention — which can escalate into obsession — makes the forbidden food seem very important. Your inner brat takes advantage of this, and tries to convince you that you MUST have that chocolate or pizza.
2. Perceived scarcity: When something is scarce or in short supply, its perceived value increases. You want it more because you think other people also want it. If you’ve ever bid at auctions or on eBay, you know the experience of that last-minute excitement as you watch the bids spiral upward. The more people who bid, the more you’re willing to pay for the item. Your inner brat wants it at any price.
3. “Psychological Reactance”: People don’t like to be told they can’t have or can’t do something. It’s related to not wanting to be controlled by others, especially if the situation feels unfair or arbitrary. The “reactance” is both emotional and behavioral.
The emotional part is your inner brat saying, “Oh yeah? I can’t have what I want? Just try to stop me!”
The behavioral component is what you do about it, which usually involves some type of rebellious reaction. You see this with teenagers whose parents have forbidden them to date certain people. Reactance also explains why a “Wet Paint” sign always invites unwanted fingerprints on the newly painted surface.
Next time you don’t get what you want, ask yourself whether one of the above factors has influenced your desire. If so, let go of the pursuit. Your inner brat won’t be happy, but ultimately (in the words of the Rolling Stones,) you “might just find [that] you get what you need.”
The SQL Server Reporting Services … service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Sound familiar? It was a problem I was having with a couple of SQL Server 2008 R2 machines built on VMWare 5.1 hosts. The SQL Server Reporting Services don’t start automatically on reboot and won’t start when manually instigated.
Fortunately it can be easily remedied by increasing the default service time-out:
- Open Regedit
- Navigate to: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- Create a new DWORD value called ServicesPipeTimeout
- Modify it and ensure it is set to Decimal and enter the value 60000
- Close Regedit and reboot the server
Note: Incorrect modification of the registry can lead to serious problems, please be careful. For protection it’s worth taking a backup of the registry before hand.
If this does not work then you may have a more serious issue, if this is the first time you have tried to start the service then double check you have met the prerequisites for installation and have it configured correctly.
This blog was copied from: http://sysbadmin.wordpress.com/2013/03/25/how-to-fix-non-starting-sql-reporting-services/
Whenever you make a fundamental change to a DNS zone it’s a good idea to back it up, but how do you do that when your DNS is Active Directory Integrated without taking a system state backup? We’ll take a look at both AD integrated and standalone methods to get a better understanding.
Non-AD integrated (Standalone) DNS:
If you’re running standalone DNS and simply have a Primary/Secondary setup then performing this style of backup is really very simple. As standard DNS zone file information is stored in the
%systemroot%\system32\dns folder (typically
C:\Windows\System32\dns). When the DNS service starts it simply loads the dones from these files, likewise when a change is made it creates a backup and places it in the backup folder on the aforementioned path. It’s worth noting that only one backup is maintained so if you make another change the previous backup is overwritten, therefore if you make a sideways copy of these backups you can keep a version as long as you need.
AD Integrated Zones:
As AD integrated zones are stored within the Active Directory they do not have any files associated with them and therefore are not backed up to the backup directory. So how do we get it out? Using DnsCmd.exe is how!
The Microsoft example of a zone export is as follows:
dnscmd  /zoneexport
This looks great but here it is in a more useful looking format:
DnsCmd DNSserver1 /ZoneExport example.com example.com.bak
Note that the backup file you have created will land in
How to restore AD Integrated Zones:
Warning: You should only attempt to restore this file as a last resort as it could impact your users especially then allowing for replication to the DNS holding DC’s.
- Hop onto the DNS Management Console and delete the zone
- Rename your zone backup to have a .dns extension, in the example above this would go from
- Create a new zone with the FQDN of the zone you deleted, if using the New Zone Wizard be sure to uncheck the Store in Active Directory option.
- When prompted to create a new zone file or use an existing file, choose an existing file, the wizard should automatically fill in the zone FQDN with the .dns extension, this should look the same as your renamed zone file (
- Complete the wizard
- Check the zone information is as per the zone before the changes
- If all is well, simply change the zone type to Active Directory Integrated.
So you’ve been taking a look at what’s eating your hard drive space with WinDirStat or TreeSizeFree or similar and have spotted the C:\Windows\Winsxs folder.
Winsxs stands for Windows Side by Side and is basically where Windows keeps multiple versions of the same .dll’s to allow multiple applications to run without any compatibility problems. If you browse it you’ll see what looks like a lot of duplicate .dll files. I’m not going to go into the in’s and out’s of it here as there are plenty of good run through pages on the web.
What I will do is give you the easy and safe way to clear it down.
From the C:\Windows\System32 folder run:
DISM /online /Cleanup-Image /SpSuperseded
This blog was copied from: http://sysbadmin.wordpress.com/2012/10/14/how-to-clean-up-cwindowswinsxs/
So, you get on site and no one knows where their NTP server is, there’s a quick and easy way to find out.
The old schoolers will tell you to use the net time commmand, but this was deprecated and is no longer recommended for use by Microsoft.
If you still want to use it or you’re on a Windows Server 2000 box
- Open up a command prompt
- Type: net time /query \\serveryouwanttoquery
If you’re on anything newer:
- Open up a command prompt
- Type: w32tm /query /computer:computeryouwanttoquery /source
- If you’re having trouble w32tm.exe is found in “C:\Windows\System32″.
W32tm.exe is a powerful little tool that not only allows you to check the basic status but also completely configure the NTP server/service to whatever your heart desires. For more, check out this technet article over at the Microsoft site.
This blog was copied from: http://sysbadmin.wordpress.com/2012/09/27/how-to-find-your-local-ntp-server/