Posts

Showing posts from April, 2013

Windows Server 2008 + Knowing what is in your AD Tool Kit

Image
Work in progress… AD Recycle bin http://koppihle3.blogspot.com/search?q=recycle AD Tombstoning   http://technet.microsoft.com/en-us/magazine/2007.09.tombstones.aspx Video 1 of 1 (demo on restoring an AD object) http://www.youtube.com/watch?v=hs3YqQVv-M0 AD LDS backup (Windows Backup or dsdbutil) http://technet.microsoft.com/en-us/library/cc730941(v=ws.10).aspx AD LDS restore (Windows Backup or dsdbutil) http://technet.microsoft.com/en-us/library/cc725903(v=ws.10).aspx AD LDS editing http://technet.microsoft.com/en-us/library/cc732675(v=ws.10).aspx AD AD LDS Snapshots step by step http://technet.microsoft.com/en-us/library/cc753609(v=ws.10).aspx Video 1 of 4 (explanation of who what and why) http://www.youtube.com/watch?v=36cqfV38Q5Y Video 2 of 4 (minute 6 is start of demo of process) http://www.youtube.com/watch?v=JUoiq_wYSUg ' Video 3 of 4 (this is video is the gold of the demo) http://www.youtube.com/watch?v=dQxCjmh_v8E Video 4 of 4 (continued explanation including limitat

Server 2008 R1 Backup Setting up Email Alerts

Image
This will provide you basic alerting based on the events you select. If you setup events for every possible backup event this will take some time. I would more likely setup the most common success and failure warning. Before proceeding you must have an SMTP server configured internally and ready to use: Open event viewer Select “Applications and Service Logs”> “Microsoft”>”Windows”>”Backup”>”Operational” as shown below: Note: Before we start let me preface this with you do not want to “Attach a Task To this Log…” on the root of “Operational”, though it is possible, because it gives you NO information other than something posted to the backup operational log. So it will send you lots of emails with no information. You might as well just check the server logs daily. So go to the Successful backup task in our event logs “ Event ID 4 ” as shown below: Right Click and select “Attach Task To This Event…” as shown below: “Next”: “Next”: Select “Send and e-mail” as sown below

Server 2008 SMTP Relay through GMX as a Smarthost

Image
Access your SMTP configuration using IIS 6.0 Manager as shown below: Select the SMTP server as shown below: Right Click and select Properties: The “Access” tab is how you lock down what is sending through your SMTP server by limiting the Authentication, Connection, and Relay Settings as shown below: For Example the setting below will only allow the address 192.168.0.2 to connect to the SMTP server: Another Example the setting below will only allow the address 192.168.0.2 to relay through the SMTP server and allow authenticated is unchecked: Now to configure our relay I assume by this time you have already setup a free email account with www.gmx.com Select the “Delivery” tab and “Outbound Security” as shown below: Select “Basic authentication” and enter in your GMX.com username and password as shown below and click “OK”: Note : if using other email providers as a SMTP relay you may need to enable TLS (check with your email provider) You should not need to Modi

Server 2008 R1 SMTP Installation

Image
To install SMTP go to “Server Manager”>”Add Features”> and install ” SMTP” Note: I recommend installing the feature “Telnet Client” as well to aid in troubleshooting later. After the installation completes to manage SMTP and FTP on Server 2008 R1 you must use IIS 6.0 Manager as shown below: When using the IIS 6.0 MMC when you open SMTP you will likely receive the error “ No Such Interface Supported ” . This is a common problem to fix it open a command prompt as an administrator and register the DLL’s using the following command: C:\Windows\System32\inetsrv>regsvr32 smtpsnap.dll C:\Windows\System32\inetsrv>regsvr32 smtpadm.dll Close and reopen the IIS 6.0 MMC and the error should go away. I have noticed there are some other items that are a bit off with this SMTP version such as SMTP logging does not appear to work properly. Thus the need for installing the Telnet client for testing and thoroughly locking down your SMTP environment. Please see my other SMTP conf