Click Start, select Run, type in: services.msc
then press enter
Now look for the Automatic Updates Service, right click it and choose to stop
Click Start, select Run, type in: %windir%\SoftwareDistribution
then press enter
Open the Datastore folder and delete its contents.
Virtual Server has commonly created a shared disk over the emulated SCSI controller to use for clustered storage. However, Server 2008 clustering doesn’t support parallel SCSI.
But there is light at the end of the tunnel. Server 2008 clustering supports the majority node set model, which means a cluster doesn’t need shared storage. Server 2008 can use node-voting with three nodes or more, or a file-share witness instead of the quorum disk for two-node clusters.
You can use this simple batch file to rename a file and append today’s date:
set Day=%Date:~0,2%
set Mth=%Date:~3,2%
set Yr=%Date:~6,4%
rename c:\test.log test_%Day%-%Mth%-%Yr%.log
t’s common to install the SMTP service on servers that require limited mail-sending capabilities–for example, on a Microsoft SharePoint server. I recently had a problem in which the box got a new IP address, and at that point the services that used the SMTP service could no longer send email. The problem was that the server had a relay restriction list in place, and the list didn’t have the new IP address listed.
To resolve the problem, you need to update the relay list. Start the Microsoft Management Console (MMC) Internet Information Services Manager snap-in by accessing Start, Programs, Administrative Tools, Internet Information Services (IIS) Manager. Right-click the SMTP virtual server and select Properties, then select the Access tab. Click the Relay button. Be sure to add the IP address of the server trying to connect or a subnet containing the servers trying to send via the server by clicking the Add button. When you’re finished, click OK on all dialog boxes.
The transaction log size in Exchange 2007 is now 1MB instead of 5MB, which was the transaction log size for Exchange 2003. The reason for the size reduction is related to the new log shipping clustering technologies in Exchange 2007. The smaller the log file means a smaller amount of data loss because you can’t ship a transaction log until it’s closed and it needs 5MB of data written before you can close. With Exchange 2007, you only need 1MB of data written. In addition to the reduction of size of the transaction logs the naming scheme has been changed from E<2 digit storage group identifer><5 hexidecimal digits> to E<2 digit storage group identifer><8 hexidecimal digits> which means even though there will be five times the number of transaction logs the number of transaction logs you can have in total is over two thousand times the number of transaction logs you could previously have under Exchange 2003 (you don’t go all the way up to ffffffff, rather 7fffffec).
Extracting the SMS Installer-ISU integrated download (or, just the standard SMS Installer) requires that a SMS site server be present on the network connection. When the extraction intiates is asks for a valid server name and will check to see if its available.
Say, you downloaded SMS Installer from home on a dial-up connection, what do you do then? Wait until you are in the office?
Windows automatically limits access to the Security log to only those users who have the Manage auditing and security log user right. However, guests can access the System and Application logs. To disable guest access to these logs, open a Group Policy Object (GPO), go to Computer\Configuration\Windows Settings\Security Settings\Event Log\Settings for Event Logs, and enable Restrict guest access to system log and Restrict guest access to application. In Windows Server 2003 and Windows XP, these policies are named Prevent local guests group from accessing system log and Prevent local guests group from accessing application log, respectively. Other users will still be able to view these logs provided they possess the Access this computer from the network user right. Windows doesn’t offer a more granular way to control access to the logs.
I fixed this problem by simply removing invalid entries from my system path. When Windows Explorer starts, it traverses the PATH variable, and invalid entries can extend the time necessary for Windows Explorer to initiate. To solve the problem, you need to ensure that each item in your PATH variable exists. To do so, open the Control Panel System applet, and access the Advanced settings (on the Advanced tab). Click the Environment Variables button. Under System Variables, view the PATH variable and check each entry that makes up the path. (Entries are separated by a semicolon.) Remove any incorrect entries, and click OK. Click OK on the main Environment Variables dialog box.
Recent Comments