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.

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

http://blogs.msdn.com/b/astebner/archive/2010/12/22/10108400.aspx

Question:

I used the instructions and the cleanup tool in this blog post to remove all versions of the .NET Framework from my computer, and now I want to re-install them.  Do I need to re-install them in any specific order?

Answer:

In general, the versions of the .NET Framework allow you to install in any order you choose.  However, I recommend installing in reverse order from newest to oldest, like this:

1. .NET Framework 4
2. .NET Framework 3.5 SP1 (this will install the .NET Framework 2.0 SP2 and 3.0 SP2 behind the scenes so you do not have to install them separately)
3. .NET Framework 1.1 (if you have any programs installed that need it, this blog post can help you decide whether or not you need it)
4. .NET Framework 1.0 (if you have any programs installed that need it, this blog post can help you decide whether or not you need it)

Even though it is a little counter-intuitive, there are a couple of reasons that I recommend installing in reverse order:

• To help avoid some possible setup bugs in older versions of the .NET Framework – there are a couple of setup bugs (like this and this) in older versions of the .NET Framework that are fixed in service packs and later versions.  Installing a later version of the .NET Framework first will update some files that are shared by all versions of the .NET Framework, and that will allow you to avoid these bugs when installing older versions of the .NET Framework.
• To minimize the number of separate downloads and installs – if you install the .NET Framework 3.5 SP1 first, it will automatically install the .NET Framework 2.0 SP2 and 3.0 SP2 for you, so you don’t need to install them separately.  Also, if you install older versions of the .NET Framework 2.0 and 3.0 before installing the .NET Framework 3.5 SP1, the 3.5 SP1 installer will automatically uninstall them as a part of its install process.  That means you will just end up wasting time if you install the .NET Framework 2.0 and 3.0 before installing the .NET Framework 3.5 SP1.