It is now possible to create a new VHD or attach an existing VHD to your Windows server 2008 R2…
There are some other features that you can do but it was possible also in non R2 version… That is shrinking and extending partition using Disk Management
Sometimes you delete user from AD and it could cause a big headache 
Well… No more. Windows server 2008 R2 Beta – which is by the way already publicly available has a new functional level for AD that allows you to activate so called Recycle Bin Feature…
In this demo you will se my AD server with a domain called demoadps.local on which I will enable this feature. As I mentioned before – functional level should be Windows server 2008 R2.
First of all you need to enable the feature by typing a Powershell cmdlet/command:
Enable-ADOptionalFeature ‘Recycle Bin Feature’ -Scope Forest -Target ‘domain.local‘
after that you can check for deleted items by typing:
Get-ADObject -SearchBase “CN=Deleted Objects,DC=domain,DC=local” -ldapFilter “(objectClass=*)” -includeDeletedObjects | FT ObjectGUID,Name -A
This will show you the deleted objects which you can restore by entering:
Restore-ADObject -Identity 6ff46162-15c2-4d42-8e15-2fcac5c8422e
** domain.local should be changed with your domain name
6ff46162-15c2-4d42-8e15-2fcac5c8422e should be changed with a ID that matches your deleted object…
To make it simplier I have recorded a video tutorial to do that…
New SMB 2.0 allows higher speeds when transfering files between Windows server 2008 machines and Windows Vista machines.
On gigabit network we can see a drastical improvement in speed and network performance. SMB2.0 allows ACK packets to be sent only after 16 megabyte of data…
You can access harlink-ed files and Directory junction folders over the network… Even if files and folders are not shared (only “linked” to one of your shared folders …)
Making SYMLINK without any parameters using MKLINK command
Making SYMLINKD using MKLINK /D command
Making HARDLINK using MKLINK /H command
Making JUNCTION using MKLINK /J command
When you are using this command you should know that …
This video will show you how to setup Failed request tracking and see the results when something goes wrong on your server…
This video will show you how to install PHP on IIS7.0 and test it with example (phpinfo();)
Installing PHP on IIS7.0 on Windows server 2008
http://blogs.iis.net/bills/archive/2006/09/19/How-to-install-PHP-on-IIS7-_2800_RC1_2900_.aspx
In this video tutorial you will see how to install IIS7.0 on Windows server 2008 (RC1).
This video was created to show you installation of PHP into IIS7.0 afterwards…
Windows server 2008 / IIS7.0 Installation
Before you decide upon a website hosting deal, confirm if the web server is compatible with your dsl, so that your web site design can be enjoyed by all.
Osnovna pravilna konfiguracija DNS zapisa in njegovo testiranje. / Correct basic configuration of DNS records and testing.
Pri konfiguraciji DNS strežnika moramo upoštevati nekaj osnovnih navodil. There are some basic rules that should be folowed when configuring DNS servers.
Vzemimo primer, da imamo domeno company.com za katero bi radi naredili DNS zapis: Let say that we have domain company.com and we would like to create DNS record for it:
1. naredimo primarno forward cono company.com / create forward zone for company.com
2. popravimo SOA zapis: / correct SOA record:
2.1 oštevilčimo po principu LETOMESECDAN01 – primer: 2007020701 / enumerate it with YYYYMMDDnn
2.2 vpišemo ime primarnega DNS streznika ter e-mail skrbnika domene – pozor v obliki ime.domena.končnica – brez afne – @ / enter the name of primary DNS server for domain company.com and its hostmaster without “at” sign – @ example. hosmaster.company.com
2.3 po potrebi popravimo časovne vrednosti zapisa / if it is needed fix the time values of the record
2.4 vpišemo DNS strežnike / enter your DNS servers
3. naredimo zapis gostitelja – A zapis strežnika, ki bo gostil storitve / create a HOST or A record for a computer that will host services
4. naredimo psevdonim – CNAME zapis, ki bo “kazal” na gostitelja. / create alias – CNAME record for aliases that will point to HOST.
5. naredimo MX zapis za domeno company.com / create MX record for domain company.com
6. testiramo delovanje z uporabo / testing:
ping
nslookup
http://www.dnsreport.com – preverite nastavitve svoje domen / check your domain name configuration
http://www.dnsstuff.com – dodatna orodja za pregled DNS zapisov / additional tools for checking DNS records
Izdelava forward cone z nekaj zapisi / Creating forward zone with some records
(wink source)
Konfiguracija Exchange 2003 SP2 strežnika za filtriranje proti črnim listam, uporaba Intelligent message filter-ja ter Sender ID procesiranje / Configuration of Exchange 2003 SP2 to filter mail using black lists, usage of Intelligent message filter and Sender ID processing
Nekaj zlatih pravil na katere moramo biti pozorni pri konfiguraciji poštnih strežnikov. / Some rules to be aware of when configuring mail servers.
DNS nivo / DNS layer
1. MX zapis mora obstajati / MX record must exist
Za test lahko v ukazni vrstici vpišete ukaz / For testing you can try to get the MX record using nslookup command:
nslookup
set type=MX
company.com
Kot rezultat bi morali dobiti / As result you should get:
company.com MX preference = 10, mail exchanger = mail.company.com
2. Forward in reverse DNS zapis se morata ujemati / Forward and reverse DNS record must be the same
Primer / Example:
Recimo, da MX zapis za domeno company.com kaže na poddomeno domene company.com in sicer na mail.company.com. V primeru, da izvršimo ukaz ping v ukazni vrstici dobimo rezultat: / Let say, that MX record for domain name company.com points to subdomain of company.com – mail.company.com. In this case you can check by pinging hostname and get the result:
C:\>ping mail.company.com
Pinging mail.company.com [123.123.123.123] with 32 bytes of data:
Reply from 123.123.123.123: bytes=32 time=119ms TTL=238 …
Ce pa izvršimo ukaz, ki nam iz IP naslova razreši DNS zapis moramo dobiti rezultat: / If we try to make a reverse lookup we should get the same result:
C:\>ping -a 123.123.123.123
Pinging mail.company.com [123.123.123.123] with 32 bytes of data:
Reply from 123.123.123.123: bytes=32 time=111ms TTL=238
…
Nivo poštnega strežnika (SMTP strežnika) / Mail server layer (SMTP server)
SMTP strežnik se mora oglasiti z istim imenom, kot je vpisan v MX zapisu – v našem primeru: mail.company.com. To pa lahko preizkušamo tako, da se z uporabo programa telnet povezemo na poštni strežnik na portu 25. / SMTP server should present with the same name as a name in MX record. In our case this is mail.company.com. This can be tested using telnet program connecting to port 25 of our mail server.
Kot rezultat bi morali dobiti: / As a result you should get:
220 mail.company.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Mon, 5 Feb 2007 23:07:34 +0100
http://www.dnsreport.com – preverite nastavitve svoje domen / check your domain name configuration
http://www.dnsstuff.com – dodatna orodja za pregled DNS zapisov / additional tools for checking DNS records
http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ – Sender policy framework – generator TXT zapisa / Sender policy framework TXT record generator
I. del / Part I. – Message delivery properties – general
(wink source)
II. del / Part II. – Message delivery properties – Connection filtering
(wink source)
III. del / Part III. – Message delivery properties – IMFv2 / Sender ID filtering
(wink source)
IV. del / Part IV. – Activate filters on SMTP server
(wink source)
