Backing up SQL databases in environments where is installed SQL Express version is always a difficult thing for many administrators. As we know, SQL Express doesn’t support scheduled backup like other versions, but we must do a backup with scripts. This is not so friendly and we would like to be able to make backups with some software, without scripting. I found a free program, called SQLBackupAndFTP, for backup databases for this cases. You can download it from their website.
The program is very simple to use, it works and it also has a lot of good functions. Of course for using all functions, you must pay them..
Tag: Small Business Server
DNS Error 7600 in Windows Server 2008R2
It is very common to have the Error 7600 (Warning) in DNS Server installed on Windows Server 2008R2 in environment where is also present the Microsoft Tread Management Gateway. If you look for this error on internet, in most cases, is classified as “Nothing serious, leave it”, but I don’t like this solution.
Additional research showed me, that the cause of this error are two records from TMG: WPAD and ISATAP, which are blocked with the new function of DNS (DNS Block feature), introduced in the version Server 2008. If this is true, the correction it is very simple:
- First you must check if the block feature is really enabled. You can do this from command prompt (don’t forget to run as administrator!) with the simple command dnscmd /info /enableglobalqueryblocklist. If the result is 1,the feature is active.
- Then you can check which addresses are blocked with the command dnscmd /info /globalqueryblocklist. I’m sure, that you will find wpad and isatap on list.
- Now you have two options to solve the issue. First one is to disable the feature with executing dnscmd /config /enableglobalqueryblocklist 0. The second one is to clear all names from blocking list with the command dnscmd /config /globalqueryblocklist. Later you can add some names with the command dnscmd /config /globalqueryblocklist name1 name2 name3. You must specify all blocked names together. The old list will be replaced every time you will execute that command.
And don’t forget to control all DNS servers!.
Removing standard SBS errors listed in reports
Install Terminal server on Windows Server 2008R2 DC
For the first thing, I want to underline that installing a terminal server on a domain controller is not a best practice and is not a very good idea. But in some cases, in small environments, where you have maybe only one or two servers, you have no choice and you must to do that.
It’s not a problem to install a rule, but you will have a problem when you will try to logon through terminal services with a user who is not an administrator. There you will receive the error that this user is not the administrator and it has no logon true terminal services rights. On a non-DC server, this is simple to solve in local users and groups console, but this users and also the console is disabled on a DC.
You must do that in gpedit.msc. There you have to enable Allow Logon through Terminal services right to the desired group of users (look at the picture).
You must think also about the printing issue. There is a security issue on Spool folder, because the user does not have sufficient rights on it. To solve this problem, you must open a Command prompt as Administrator and go to the folder C:WindowsSystem32spool. Here you have to run the command Cacls.exe PRINTERS /e /g users:C and restart the computer. Now you are able to print.
Good luck..
Maintaining WSUS 3.0 with scripts
Every month we have more and more updates to download to our servers and the result is more and more space used. This is why we must frequently and automatically take care of our system.
To free some space with the deletion of unused and unneeded updates, exist on TechNet a script and you can automate this step using a scheduled task and a batch file. A sample of bat file is attached.
On TechNet is also available a script to maintain health status of the SUSDB database. As in previous suggestion, I recommend to execute this step with a scheduled task and a command like:
sqlcmd -S “SQL_Server/Instance” -E -i”<Location>Script.sql” -o “<Location>DB_Output.txt”
If you have a SBS server or another system, based on Windows internal database, the correct syntax is:
sqlcmd -S ” np:.pipeMSSQL$MICROSOFT##SSEEsqlquery ” -E -i”<Location>Script.sql” -o “<Location>DB_Output.txt”
This line will establish a trusted connection to SQL Server,execute the script and write all outputs to the DB_Output.txt file. Switches are case sensitive!
This operation will maintain your server in good conditions and always clear, without unneeded updates. I recommend to run this scripts every two or three months, it’s not necessary to run them more frequently.
