Did you ever bumped into this Non Delivery Report ?

#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service
reported an error.  The following information should help identify the cause
of this error: "MapiExceptionNotAuthorize

This is mainly caused by the wrong permissions of either Anonymous (for external sent mail) or Default (for internal sent mail).

External senders will receive the error if the Public Folder does not permit “Anonymous” to create new items.

[PS] C:\>Get-PublicFolderClientPermission \test

Identity                   User                       AccessRights
--------                   ----                       ------------
\test                    Default                    {FolderVisible}
\test                    mycompany.local/Users/A... {Owner}
\test                    Anonymous                  {None}

To grant this access run the following command in the Exchange Management Shell.

[PS] C:\>Add-PublicFolderClientPermission \test -User Anonymous -AccessRights CreateItems

Identity                   User                       AccessRights
--------                   ----                       ------------
\test                    Anonymous                    {CreateItems}

Internal senders are able to be authenticated by the Exchange server, and so are not treated as Anonymous. For internal senders the user must have at least Create Items permissions on the Public Folder. For general use Public Folders this can be granted as the “Default” permission.

To grant this access run the following command in the Exchange Management Shell.

[PS] C:\>Add-PublicFolderClientPermission \test -user Default -AccessRights CreateItems

Identity                   User                       AccessRights
--------                   ----                       ------------
\test                     Default                     {Contributor}

Now to see the name of the public folder (in this example is test) you can go in the public folder console in found in tools under exchange management console. Expand the default public folder and see their names.

First off there are 2 ways to do this.

The first one is for the Exchange 2010 NON SP1 and I will not cover it because it involves either dangerous techniques or a second machine with Office 2010 64 bit and Exchange 2010 management tools. You can find the “how to”  here.

The second way is dedicated for Exchange 2010 SP1.

1. Start the Exchange Management Shell

2. Give the user you are logged on with role assignment using the command below. (AdminExchange is my user in this situation)

New-ManagementRoleAssignment -Role “Mailbox Import Export” -User AdminExchange

3. Start he export of the desired mailbox using this command:

New-MailboxExportRequest -Mailbox Jan@domain.nl -FilePath \\Server\share\jan.pst
The mailbox can also be an alias or the full e-mail account and the filepath needs to be a share (if it’s not a share you’ll get an error regarding the path).

If you have a large mailbox it will take longer. Don’t close the management shell until it’s finished.

If by any chance you “accidentally” delete and “accidentally” click YES on the pop-up asking if you are sure if you want to delete the website, here’s what you may want to try.

First of all for the sake of the argument let’s say you don’t have a backup configuration file.

If you right lick the server All Tasks -> Backup/Restore configuration you can select one of the previously created configurations. They are done automatically so you should have at least 6 previous versions, or the initial setup if the others aren’t working.

Second scenario imply that you saved too many configurations in the property pane of the pages trying to put it back that no backup configuration will help you anymore. In this case you should have a physical backup of the files and folders of the C drive. A snapshot or a .bck will do the trick as long as they are browse able. You need to explore the backup and go to windows->system32->inetsrv and copy the file Metabase.xml . Run a command prompt and stop all the IIS services with the command NET STOP IISADMIN /Y . After all the processes are stopped go to C:\Windows\System32\Inetsrv , find Metabase.xml and rename it to something like Metabase.xml_1 (doesn’t matter, it’s just to keep both versions) and paste the file that you got from the backup. Go to the Services pane (run -> services.msc) and start all the services that are on Automatic (check the list of stopped services from the command prompt earlier used). This should be all you need to get it up and running again.

Let’s say that you are not running the Exchange server on the C drive therefore the most probable cause of disk space running out on the C drive isn’t the all so popular transaction logs. Let’s say it’s something else that you just can’t figure out.Here are some popular tricks to fix this issue quick :

1. First of all try running cleanmgr.exe and see if you have any temp files that you could get ridd of and use it to clean it all.

2. Windows keeps old instalation files in a folder called located at c:\windows\installer . Now cleaning this folder by deleting the content it’s probably going to render windows unninstall corrupted in many application cases but there is a way to safly do that. It’s by using msizap.exe . After you download it (you can simply click the hyperlink above) just open a cmd and navigate to the location of your msizap.exe and type in “msizap.exe G! “. This option will remove orphaned cached Windows Installer data files (for all users). This thing here will save you a lot of space depending on how old is the windows instalation and how many programs have you used over time.

3. Everytime your computer is being updated, windows automatically saves the installation cache in a folder:

• C:\Windows\SoftwareDistribution\Download

Now you can do this manually from time to time or you can create a login script. All you have to do is :

CD\
CD %Windir%
CD SoftwareDistribution
DEL /F /S /Q Download

Now that you have the .bat file paste it in c:\windows\system32 and afterwords go in active directory users and computer, under your username (or the adminsitrator username) under the profile section user profile -> Logon script and typein the Erase_cache.bat. That’s it!

Daca toate serviciile sunt pornite, conectorii de SMTP sunt ok, cozile de livrare de asemeanea si toate lucrurile par sa fie ok iar mailurile dvs nu mai pleaca verificati spatiul disponibil pe C:\ sau pe drive-ul unde este instalat Microsoft Exchange 2007. Chiar daca aveti undeva intre 2 si 10 Gb este foarte probabil ca exchange-ul sa fi oprit serviciul de mail submission datorita faptului ca nu mai are spatiu. Pentru a verifica cel mai rapid utilizati un telnet catre server (ex : start-> run-> cmd-> telnet-> o localhost 25-> helo “localhost name” -> mail from: zzz@ccc.com .. etc). In momentul in care ati introdus adresa expeditorului va aparea o eroare 4.3.1 Insufficient System Resources . Traducerea cea mai simpla este ca mechanismul de verificare al exchange-ului a ajuns la concluzia ca systemul ramane fara resurse motiv pentru care a oprit serviciul de mail submission. Ca sa reparati problema rapid (pana eliberati spatiul necesar) mergeti in mmc-ul Services (start ->cmd -> services.msc) si opriti serviciul MSExchangeTransport , apoi navigati catre \Exchange Server\Bin\ si editati fisierul EdgeTransport.exe.config cu un editor text. Gasiti linia <add key=”EnableResourceMonitoring” value=”true” /> si modificati valoarea din true in false. salvati fisierul si reporniti serviciul MSExchangeTransport. Trimiterea mailurilor va fi repornita imediat

Sa presupunem ca aveti un server nou, pe care tocmai ati instalat ESX si doriti sa instalati o masina virtuala bineinteles folosind chiar cd-ul primit de la producator si in loc de un instalation welcome screen vedeti un mesaj : “This system is not supported platform”. In principal trebuie sa stiti ca asta veti pati cand nu folositi ESX customizat de catre producator (dell, hp, etc.), asa cum a fost cazul meu deoarece HP nu a reusit sa lanseze esxi 4.1 customizat motiv pentru care am mers cu varianta default de la vmware. Rezolvarea acestei probleme este cat se poate de usoara :

Pasul 1 : Inchideti masina virtuala.

Pasul 2: Edit Settings

Pasul 3: Options ->Click pe Advanced General -> Configuration Parameters -> Add row

Pasul 4: Completati smbios.reflecthost=”TRUE”

Salvati si porniti masina virtuala.

Acest post este dedicat celor care au intampinat aceasta eroare la instalarea office-ului 2007 sau a altor aplicatii pentru ca tin de aceeasi problema a Microsoft-ului .. Dupa cateva minute de la rularea installerului de la office apare o eroare “the windows installer service cannot update one or more protected windows files”, dupa care installerului face roll back si se opreste.
Primul lucru pe care ar trebui sa-l faceti cand intalniti erori de rulare, instalare sau orice altfel de erori de la windows -> click dreapta pe my computer ->manage ->event viewer->application. Aici am gasit urmatoarea eroare “Product: Microsoft Software Update for Web Folders (English) 12 — Error 193 The Windows Installer service cannot update one or more protected Windows files. SFP Error: -536870654.
List of protected files: C:\program files\common files\microsoft shared\web server extensions\40\bin\fp4autl.dll”

Am cautat ce s-a intamplat cu fisierul mai sus mentionat si am descoperit ca lipsea. Cel mai simplu de gasit este in cd-ul cu windows in folderulu I386 (de reugla il veti gasi in radacina cd-ului sau imaginii, daca nu dati un search in cd ), cautati fisierul FP50EXT.CAB, se poate deschide cu winrar-ul, iar din acest CAB copiati fisierul fp5autl.dll in c:\program files\common files\microsoft shared\web server extensions\40\bin\ si reporniti instalarea. (daca nu aveti un cd cu windows la indemana gasiti fisierul aici fp4autl.dll

Recent a trebuit sa rulez o masina virtuala, in cazul meu un vmc pe o platforma de windows deja virtualizata. In traducere trebuia sa fac o virtualizare in virtualizare. Dupa ce am incercat sa folosesc Virtual Pc de la Windows am intampinat cateva erori de compatibilitate si atunci am apelat la VMware Player. Acesta din urma este gratuit insa in momentul in care vrei sa rulezi virtualizarea primesti o eroare “Running VMware Player in a virtual machine requires the outer, virtual machine to be configured for running a VMware ESX guest operating system. You may not power on a virtual machine until the outer virtual machine is reconfigure.”.
Iata in ce consta reconfigurarea masinii virtuale (the outer virtual machine):
Pasul 1 : Inchideti masina virtuala corespunzator.
Pasul 2 : Conectati-va la serverul de ESX da-ti click dreapta pe masina virtuala -> edit settings -> options -> advanced -> general ->click pe butonul “Configuration parameters”
Pasul 3 : In fereastra care va aparea modificati deploymentPlatform din “windows” in “vmkernel”
Pasul 4 : Adaugati o valoare noua dand click pe butonul din coltul din dreapta jos
Valoarea din coloana din stanga trebuie sa fie : monitor_control.vt32, iar in coloana din dreapta completati cu TRUE
Pasul 5 : Adaugati o valoare noua dand click pe butonul din coltul din dreapta jos
Valoarea din coloana din stanga trebuie sa fie : monitor_control.restrict_backdoor , iar in coloana din dreapta completati cu TRUE
Pasul 6 : Inchideti fereastra de configurare si porniti masina.

Dezafectarea unui domain contoller impune mutarea serviciilor de domeniu stocate in prezent pe server pe un alt domain conttroller

Transferarea rolurilor FSMO.

• Transferarea Rolurilor principale de domain controler : RID, PDC si Infrastructure Master
  1.   Mergi in Start , Programs,  Administrative Tools si selecteaza Active Directory Users and Computers.
  2.   Click-dreapta pe  Active Directory Users and Computers si selecteaza Connect to Domain Controller.
  3.   Selecteaza domain controller-u pe care vrei sa transferi rolurile si apasa OK
  4.   Click-dreapta pe Active Directory Users and Computers si selecteaza Operation Masters.
  5.   In fereastra Change Operations Master selecteaza tabu-ul RID si apasa butonul Change. 
  6.   Apasa OK pentru confirmarea transferului.
  7.   Repeta etapa 5,6 si pentru taburile PDC, Infrastructure Master.
  8.   Acum apasa Cancel pentru a inchide fereastra.
• Transferarea rolului Domain Naming Master
  1.   Mergi in Start , Programs,  Administrative Tools si selecteaza Active Directory Domains and Trusts.
   2.   Click-dreapta pe Active Directory Domains and Trusts si selecteaza Connect to Domain Controller.
  3.   Selecteaza domain controller-u pe care vrei sa transferi rolu si apasa OK
  4.   Click-dreapta pe Active Directory Domains and Trusts si selecteaza Operation Masters.
  5.   In fereastra Change Operations Master apasa Change
  6.   Apasa OK pentru confirmarea transferului.
  7.   Apasa OK
  8.   Acum apasa Cancel pentru a inchide fereastra.
• Transferarea rolului Schema Master
  1.   Mergi in Start selecteaza run, tasteaza mmc si apasa OK
  2.   In meniul consolei selecteaza File si apasa pe Add/Remove Snap-in.
  3.   Apasa Add.
  4.   Selecteaza din stanga Active Directory Schema.
  5.   Apasa Add (butonul din mijocul ferestrei)
  6.   Apasa Close pentru a inchide fereastra Add Standalone Snap-in
  7.   Apasa OK pentru a adauga interfata in consola.
  8.    Click-dreapta pe Active Directory Schema si selecteaza Connect to Domain Controller
  9.   Apasa Specify Domain Controller , tasteaza numele domain controller-ului unde vrei sa fie tranferat rolul si apasa OK
  10. Click-dreapta pe Active Directory Schema si selecteaza Operation Masters.
  11. In fereastra Change Schema Master apasa Change.
  12. Apasa OK
  13. Apasa OK
  14. Apasa Cancel pentru a inchide fereastra.

  Transferarea serviciului de DNS.

• Daca serverul care urmeaza sa fie eliminat are serviciul de DNS instalat si e singrul din forest atunci trebuie sa instalezi serviciul de DNS pe noul domain controller si sa configurezi “clientii” sa foloseasca noul server. Daca acest server nu are serviciul de DNS activ sau mai ai inca un server de DNS atunci trebuie doar sa verifici daca clientii au in configuratia de TCP/IP noul server de DNS.

Transferarea serviciului de DHCP

• Daca serviciul de DHCP este instalat pe acest server atunci va trebui sa faci backup la baza de date sa il tai autoritatea (unauthorize). Daca nu ai serviciul de DHCP instalt sari peste acest pas.
  Pentru a transfera serviciul urmeaza urmatorii pasi.
  1.   Mergi in Start selecteaza run, tasteaza cmd si apasa OK
  2.   Tasteaza netsh dhcp server export C:\dhcpdatabase.txt all si apasa ENTER
  3.   Instaleaza serviciul de DHCP si autorizeazal (click dreapta pe server authorized)
  4.   Copie fisierul dhcp.txt (din c:\ de pe vechiul server) in c:\ pe noul server.
  5.   Intra pe noul server si Mergi in Start selecteaza run, tasteaza cmd si apasa OK
  6.   Aici tasteaza netsh dhcp server import c:\dhcpdatabase.txt all si apasa ENTER

Eliminarea Domain Controller-ului.

1. Mergi in Start selecteaza run, tasteaza dcpromo si apasa OK
2. Apasa Next.
3. Apasa Next FARA a bifa casuta cu “this computer is the last domain controller in the domain”
4. Acum va trebui sa setezi o parola pentru Administratorul local si apasa  Next.
5. Confirma optiunile alese si apasa  Next.
6. Serverul va face o ultima replicare si la final vei primi un mesaj care indica ca rolul de Active Directory a fost dezinstalat complet. Apasa Finish si reseteaza serverul.

Ca sa putem intelege efectiv ce scop are o ruta statica sau o tabela de rutare trebuie sa intelegem in prima faza ce inseamna acesti termeni. Ruta este termenul folosit pentru o defini o cale exacta catre o destinatie iar tabela de rutare este totaliatea rutelor posibile in cazul nostru pentru un calculator . De regula tabela de rutare este un tabel in care heder-ul are urmatoarele campuri ordonate astfel:  Network destination , Net mask, Gateway, Interface si Metric. Bun dupa ce am lamurit acest lucru vedem ca apar termeni noi pe care la randul lor trebuie explicati pentru a intelege procesul la un nivel mic dar totusi vom ramane cu o logica.

Network Destination se foloseste impreuna cu Netmask pentru a defini raza unei clase de IP. Primul camp
Read the rest of the entry »