Latest notes

http://community.spiceworks.com/how_to/show/264

http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx

 

[Today’s post comes to us courtesy of Damian Leibaschoff and Wayne Gordon McIntyre from Commercial Technical Support and Chris Puckett from Product Quality]

SBS 2008 installs all of its features using a single volume (C:), there are tools available to move some of the data to other locations, but a number of folders that remain in the C: volume can continue to grow if left unchecked, this can potentially eat all the available disk space on the C: drive. Once the C: drive reaches certain low space thresholds, some services will stop functioning properly on the server, while others will change their behavior to prevent data loss. Usually, administrators realize they have a problem when e-mail flow is impacted, under low disk space conditions, due to the Exchange Back Pressure features, mail flow will stop. Users may experience some of the following errors or non-delivery-reports: Error 0x800CCC6C, SMTP_452_NO_SYSTEM_STORAGE, or 452 4.3.1 Insufficient system resources. 
These are some of the steps that can be performed to help recover and prevent these issues.

IIS and SBS Logs

(This is expanding on the existing post “Reclaiming Disk Space Lost to IIS Logs on SBS 2003 and SBS 2008”)

By default, all IIS hosted web sites have logging enabled, this can lead to some large folders in C:\inetpub\logs\LogFiles (Review this post in case you have moved your log files). You may also want to specifically stop logging all together for certain web sites, in particular, the “WSUS Administration” web site (Site Id 1372222313). For this, perform the following steps:

1. Launch IIS Manager from Administrative Tools.
2. Expand Server, Sites, and select the WSUS Administration web site.
3. On the feature panel, click to open Logging.
4. Click Disable in the Actions panel (rightmost panel)
5. Repeat the steps for any other web site. Please note that logging may be needed for troubleshooting or auditing purposes on sites that are public facing, this is usually not the case on the WSUS Administration site.

Some of the SBS 2008 log files can grow to very large sizes, all SBS logs are stores in this folder (and subfolders): C:\Program Files\Windows Small Business Server\Logs\. Some of the logs that will grow the most and may need trimming are:

• Console.log, this log will continue to grow while the SBS Console is running.
• *.evtx files, these are the event logs before the setup of the server completed, they can be safely removed if the server has been in production and had no setup issues.
• W3wp.log, in the C:\Program Files\Windows Small Business Server\Logs\WebWorkplace folder. This is the log for Remote Web Workplace.
• The C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs folder. These are the logs for the Windows SBS Manager service.

POP3 Connector Badmail directory

If you are using the POP3 Connector, you may end up with emails that failed to be delivered (rejected by the local Exchange server) in C:\Program Files\Windows Small Business Server\Data\badmail. This folder will be automatically trimmed to 400mb once it reaches 450mb once a week.

The licensing log can consume a significant amount of hard disk space

This is discussed on the Windows Small Business Server 2008 Release Documentation
You can delete the events in the Windows SBS 2008 licensing log to free up additional space on the hard disk drive.

To delete events in the Windows SBS 2008 licensing log

1. From the server, open a Command Prompt window as an administrator. To do this, click Start, and then in the Search box, type command prompt.
2. In the list of results, right-click Command Prompt, and then click Run as administrator.
3. At the command prompt, type the following command: del "%systemroot%\system32\winevt\logs\Microsoft-Windows-Server Infrastructure Licensing*%4Debug.etl.*"

You can also use Registry Editor to disable the licensing log.

1. Click Start, type regedit, and then press ENTER.
2. In Registry Editor, locate and then click the following registry key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerInfrastructureLicensing
3. In the details pane, right-click TraceMask, and then click Modify.
4. In the Edit DWORD dialog box, change the value for Value data to 0 (zero), and then click OK.
5. Restart the server.

Windows Server Update Services (WSUS) Server Cleanup Wizard

In WSUS, you can delete unused updates and update revisions, computers not contacting the server, unneeded update files, expired updates and superseded updates. In order to accomplish this, you have to manually go through the WSUS Server Cleanup Wizard.
To run the Server Cleanup Wizard :

1. In the WSUS administration console (launch it from the Administrative Tools), select Options, and then Server Cleanup Wizard.
2. By default this wizard will remove unneeded content and computers that have not contacted the server for 30 days or more. Select all possible options, and then click Next.
3. The wizard will begin the cleanup process, and will present a summary of its work when it is finished, depending on the server performance, this may take a very long time. Click Finish to complete the process.

Very large SharePoint SQL transaction log file

Please read the following KB article for an explanation and instructions on how to prevent this:
2000544 SBS 2008 BPA Reports that The Windows SharePoint Services configuration databases log file is getting large (currently over 1gb in size)

Active Directory Certificate Services transaction log files

When completing a critical or system state backup of the C: volume, a new transaction log will be generated under the c:\windows\system32\certlog\ folder. Removing these logs is only safe as long as the CA database file is consistent. In order to remove these logs and reclaim disk space, follow these steps:

1. Open the Services MMC and stop the Active Directory Certificate Services service.
2. Make a backup copy of ALL the file contents present in the c:\windows\system32\certlog\ folder.
3. Delete EDB.CHK and all the files that have an extension of .LOG (*.LOG)
4. Restart the Active Directory Certificate Services service.

Windows Component Clean Tool

The Windows Component Clean Tool (COMPCLN.exe) can be used to remove the files that are archived after Windows Vista SP2 or Windows Server 2008 SP2 is applied. It also removes the files that were archived after Windows Vista SP1 was applied, if they are found on the system. Running this tool is optional.

Installing Windows Server 2008 service packs increases the amount of disk space that is used by the operating system. This space is used to archive files so that the service pack can be uninstalled. Typically, you should run COMPCLN.exe if you want to reclaim this disk space after applying SP2 and if you will not need to uninstall SP2.

NOTE: You cannot uninstall Windows Vista SP2 or Windows Server 2008 SP2 after you run this tool on an image.

Move Data Wizards

We are not going to focus on these wizards on this post, but as a reference, SBS 2008 provides an automated way of moving the following:

• Move Exchange Server Data: which moves both the exchange database file as well as your exchange transaction logs for all storage groups.
• Move Windows SharePoint Services Data: Moves the SharePoint Content and Configuration databases.
• Move Users’ Shared Data: Moves C:\Users\Shares\ directory and all sub directories 
• Move Users’ Redirected Documents Data: Moves C:\Users\FolderRedirections\ directory and all sub directories
• Move Windows Update Repository Data: Moves the repository data from C:\WSUS\WSUSContent and C:\WSUS\UpdateServicePackages. Please note it does NOT move the SUSDB Folder and the WSUS database which contains the metadata.
• More Resources:
  Manage Server Storage by using Windows SBS Console
  Moving Data on Windows Small Business Server 2008
  Introducing Server Storage Management in SBS 2008

Update #1 3/3:
Added reference to WSUS Administration web site ID (Site Id 1372222313)
Added reference to Exchange 2007 BackPressure NDRs and errors due to low disk space

http://tips-scripts.com/

http://www.messagingtalk.org/configuring-exchange-2007-accept-email-additional-domain

http://blogs.technet.com/b/sbs/archive/2008/02/28/reclaiming-disk-space-lost-to-iis-logs-on-sbs-2003.aspx

 

Today’s post comes to us courtesy of Justin Crosby and Wayne McIntyre]

Today we are going to discuss an SBS "house cleaning" tip.  If you have been running SBS 2003/2008 for awhile you may be using a lot of disk space to store old IIS logs.  This is especially true if your clients are heavy OWA, ActiveSync, RPC over HTTP, or SharePoint users.  A recent customer of mine had files dating back to 2004 and was using almost 2 Gigabytes of hard drive space to store these old logs.

To reclaim this space all you need to do is to delete the old IIS log files.  Please be sure to back them up before deleting, just in case you need the logs in the future.  I usually try to keep a week’s worth of logs and delete everything older than that.  The logs will be in folders underneath C:\Windows\System32\LogFiles\ in SBS 2003 and C:\inetpub\logs\LogFiles in SBS 2008 by default.   Additionally there is a Remote Web Workplace log stored in SBS 2008 in the following location which can grow rather large C:\Program Files\Windows Small Business Server\Logs\WebWorkplace.  If your log files are not stored in the default location, you can run the below command to determine the log file directory configured in IIS.

Note: It is inadvisable to search your hard drive(s) for *.log and delete all that you find.  Many programs actively use information stored in .log files, such as Exchange, and deleting the file may cause issues including potential data loss. 

http://www.jacksontechnical.com/article.htm?id=47

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=B134A806-D50E-4664-8348-DA5C17129210&displaylang=en

http://www.bendweb.com/blog/?p=377

http://www.windowsreference.com/security/reset-the-entire-registry-permissions-to-defaults/

 

I had some problems with my registery permissions a while ago, I couldn’t delete any thing any more, so I was looking for something that could reset my registery permissions to defaults. Here is the solution that worked for me

If you want to reset the entire registry permissions to defaults follow these steps

Note:- Before Doing any changes to registry plesae take a backup and start your changes

First you need to download SubInACL from here

SubInACL is a command-line tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this information from user to user, from local or global group to group, and from domain to domain.

Create a file with the name reset.cmd under C:\Program Files\Windows Resource Kits\Tools folder

Now you need to Edit the reset.cmd file and add the following lines

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f

subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f

Save and exit your file

Now you need to open command prompt run the following command

cdcd “C:\Program Files\Windows Resource Kits\Tools”

after this press enter and enter the following command

reset.cmd

after entering this please press enter

fter a few minutes by processing subinacl, the permission will be reset

http://blog.chriswalker.devnetonline.net/2010/04/01/migrating-plesk-windows-to-plesk-linux-a-more-simple-way?page=2

 

The right way

Plesk is pretty interesting in the way that is stores all of its information and handles things, I have to hand parallels that. If you change something on the system without doing it through plesk, its likely to get put back in 10 minutes, this happens because all of plesk’s data is stored in a mysql database. This makes it easy for us to get our passwords back. Trust me, the sigh of relief at the end of a migration and not having to deal with someone saying they cannot get access to something is much much better than having to reset passwords.

So, first, before we create the account on the target system, we’ll login to the host system. This is targeted at windows to linux, so pull up your command prompt, and get to the mysql exe/binary file.

Note this assumes that you are using the default values for everything in plesk.

Update:

I have recently discovered that the code here was actually to get the, now unsupported frontpage password in linux. I was under the impression that these were the same passwords. However, they are not. the FTP password is not viewable. Period.

/path/to/mysql -u admin -p
use psa; select domains.name, hosting.fp_adm,hosting.fp_pass from domains, hosting where domains.id = hosting.dom_id and domains.name = ':::DOMAIN NAME:::';


The above here will get you the FTP Password for the domain that is being migrated. Be sure to change :::domain name::: to the domain name.

Again in MySQL we’ll be running another command to get the control panel password (Clients password, not the domain administrator)

/path/to/mysql -u admin -p
select clients.login, clients.passwd from clients where clients.pname = ':::CLIENT NAME:::';


Here, you’ll need to know the clients name (which can probably be gotten from the hosts control panel information if you do not know it already)

So, we’ve got about half of the passwords we need now. Now we need the mail user passwords

/path/to/mysql -u admin -p
select domains.name, mail.mail_name, accounts.password from accounts, mail, domains where mail.account_id = accounts.id and mail.dom_id = domains.id and domains.name = ':::DOMAIN NAME:::';


Again, you’ll need to replace :::domain name::: with the actual domain name.

You’ll now have a list of passwords for creating a good portion of the account on the target system. Put these in the system, you’ll now have the ability to get other passwords as well, such as web users, database users, and the domain users, which are not covered here. Database users can be grabbed from the clients web data.

I hope this was informative, please feel free to leave questions in the comments section, I will either reply directly back or back on the comments page.