Information intéressante trouvée sur le blog de Mark Russinovich,

L’utilitaire NewSID est supprimé des outils depuis début Novembre,

Le post suivant de Mark Russinovich est très instructif

http://blogs.technet.com/markrussinovich/archive/2009/11/03/3291024.aspx

Source

Today, in VMM, you can open the Administrator Console and click on the Jobs view to see all the Jobs in VMM. When you select an individual job, you can click on the “Change Tracking” tab and view any changes that were recorded in VMM as part of this job.

In this post, i will show you how to do this in PowerShell since it is not as intuitive. Basically, audit trail records that are placed in the change tracking tab are not cached on the client computer by default. the only way to surface them in powershell is to individually invoke the get-job commandlet and pass it the Job parameter while asking for the FULL job to be downloaded. the following powershell script does exactly that and displayed the audit trail records for all jobs in the system.

#get all jobs in the system
$jobs = get-job -all
foreach ($job in $jobs)
{

#get the details including the audit records for each single job in VMM
$singlejob = get-job -job $job -full
$auditrecordsexist = $singlejob | select AreAuditRecordsAvailable
if ($auditrecordsexist)
{

#if any audit records exist, print them out
foreach ($record in $singlejob.AuditRecords)
{
$record
$prev = $record.Previous
$newr = $record.New
$prev
$newr
}
}
}

One of my customer’s team member had destroy the Hyper-V Cluster by mistake. He formatted the cluster nodes without evict them before doing that . The nodes of the clsuter used to be  part of old cluster that was destroyed by mistake.

I tried to build the nodes again from the scratch and Create new cluster, When I run the validation wizard I got this error:

Cluster disk with identifier (identifier) has a persistent reservation on it ,the disk might be part of other cluster. removing the disk from other validation set.

My SAN is HP EVA. The Cluster is not able to see any of my LUNS although I can see them from disk management and can’t create the cluster.

This error due to the fact that the LUNs still keeping the old identifiers from the old cluster, You have to use Cluster command line to clear the reservation by that command:

cluster.exe node %nodename% /clear:disknumber

Now everything should work fine and you can pass the validation wizard

Hi,

zur Zeit gibt es Probleme mit dem WSUS Server und dem Update KB931125 Stammzertifikate.

Den Clients wird das Update immer und immer wieder angeboten.

Lösung: alle Stammzertifikate (inkl. Mai – September) verweigern und nur das Stammzertifikate (inkl. November) freigegeben.
Auf den Clients muss dann ggf. noch folgendes ausgeführt werden:

1. Stopp des Automatischen Update oder Windows Update Dienstes
2. den Inhalt des Verzeichnisses “C:\WINDOWS\SoftwareDistribution” löschen (“rd /s /q %windir%\SoftwareDistribution”)
3. Neustart des Automatischen Update oder Windows Update Dienstes oder Neustart der Clients

Quelle: Root Certificate update KB931125 keeps installing

Na dann, Viel Spass beim selber Testen!
CU

Windows 7 and Windows Server 2008 R2 support booting from a VHD directly.  No host OS involved.  Very nice!  It kind of blows my mind a bit to think of the possibilities. 

How Does It Work?

It works like a dual boot machine, where you pick your OS option at startup.  Instead of having physical disk partitions, you can multi-boot onto a VHD instead of a disk partition.  You can boot directly to a VHD running SharePoint 2010 beta for example.   You can have as many of these as you need (and have disk space for).

For people limited to 4GB or RAM on a laptop, this can help SharePoint 2010 run much smoother because it has all the physical memory, no memory sharing with the host.  Your physical disk is available from the booted OS (VHD becomes C:, and physical disks looks like a D:, E:, etc.).  All physical hardware is available, just as if you installed the OS directly to a disk partition.

You can even get it to work with Vista as your main OS on your machine if you’re not ready to rebuild your machine with Windows 7 or Windows Server 2008 R2.  

What’s the Catch?

There are a few catches that I’m aware of: 

• It only works if the VHD is stored on an internal disk 
• The OS on the VHD must be Windows 7 or 2008 Server R2
• Hibernation and bit-locker don’t work when booted from VHD’s.  Suspend does work on my Dell D830 after I installed the NVIDEA drivers for my video card. 
• It works best with a fixed-size VHD, dynamic VHD disks will run slower
• There is a slight performance hit, around 3%, when compared to a boot from a physical disk.  It’s negligilbe, I haven’t noticed a difference at all.
• The vhd is not portable to other boxes due to hardware differences between machines.  You can sysprep and image and move it that way.

Great! Now How Do I Set It Up?

I won’t recreate a detailed walkthrough here, but the basic gist of it is this:

1. Insert Windows 7 or Windows Server 2008 R2 media
2. Boot from the CD like you’re installing the OS normally
3. At the first screen, hit Shift-F10 to open a command window
4. Use the DiskPart utility to create and mount the vhd.  Type DiskPart at the command prompt cnd enter the following commands:
   1. create vdisk file=C:\VHD-Windows7.vhd maximum=40960
   2. select vdisk file=C:\VHD-Windows7.vhd
   3. attach vdisk
   4. exit
5. Close the command prompt and continue setup
6. Select the Custom (Advanced) Install option
7. Select the VHD disk you created for the install
8. That’s it!  The Windows installer takes care of the rest.
9. If you want more control, you can use BCDEdit or EasyBCD to edit the boot menu

References

If you need a more detailed walkthrough, the best one I’ve seen is here:

• Windows 7 Formus:   Virtual Hard Drive VHD File – Create and Start with at Boot

If you’re interested in booting a Windows 7 VHD from a system running Vista (I’m not!), you might find these helpful:

• 4SysOps:  How to add a Windows 7 VHD to Vista’s boot manager menu
• Intellects: Boot From VHD – Replacing Vista or Windows 2008 Bootloader with Windows 7 Bootloader

Enjoy!

If you’ve installed the SharePoint 2010 public beta, you’ve likely run into the WCF bug. This following errors occur when provisioning Service Applications or when accessing pages that make service calls.

System.Configuration.ConfigurationErrorsException: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\<Service Area>\client.config line <Line Number>).

The service application proxy “User Profile Service Application” could not be provisioned because of the following error: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56).

You may see this error in the ULS logs after installing SharePoint 2010, or displayed on the page as an error message when provisioning service applications or accessing SharePoint pages that make WCF service calls.

How To Fix It

This is a known WCF issue when installing SharePoint 2010 on Windows 7, Windows Server 2008, or Windows Server 2008 R2.  It’s, lovingly called the WCF Sharepoint Shared Services Roll-up issue. To fix it, install a WCF OS patch:

KB971831: WCF fix for Windows Server 2008 and Vista only
http://support.microsoft.com/kb/971831

KB976462: WCF fix for Windows 2008 R2 and Windows 7
http://support.microsoft.com/kb/976462 
Note:  This link is not activated yet, but you can download the WCF fix at http://go.microsoft.com/fwlink/?LinkID=166231

If you have already installed Microsoft SharePoint Server 2010 on a server running Microsoft Windows Server 2008 R2 or Microsoft Windows 7, Microsoft SharePoint Server 2010 does not need to be reinstalled. You can install the WCF fix afterward. However, Service Applications that have been provisioned without the update installed may need to be removed and re-provisioned once the update has been successfully applied.

References

SharePoint Team Blog: Installation Notice for the SharePoint Server Public Beta on Microsoft Windows Server 2008 R2 and Microsoft Windows 7

Jie Lie’s GeekWorld: SharePoint 2010 Pre-Requisites Download Links

Windows Server 2008 supports Fine-Grained Password Policies in Active Directory, which is a huge step forward from the per-domain-only password policies of Windows Server 2003 and Windows 2000 Server Active Directory. Yet with the suggested built-in management interface for creating fine-grained policies being ADSIedit, LDIFDE, and similar utilities, and with the requirement that the Active Directory domain in question be at the Windows Server 2008 domain functional level (DFL), such policies aren’t yet deployed as widely as some people might hope.

In this article we’ll review the functionality and objects involved in fine-grained password policies (FGPP). In a subsequent article, we’ll present the use of the Windows Server 2008 R2 PowerShell v2.0 cmdlets for working with fine-grained password policies.

The Windows Server 2008 (W2K8) Active Directory schema contains some new object classes and attribute types to support fine-grained password policies. With W2K8 AD, an instance of one of these classes, a password settings container is created in the domain’s System container. In fact, the name of this container in the 777.wernerconsulting.com domain would be:

CN=Password Settings Container,CN=System,DC=777,DC=wernerconsulting,DC=com

With the Advanced Features view option enabled in Active Directory Users and Computers (ADUC), we can see this container and if there are any policies defined in it, we could work with their properties in ADUC’s Attribute Editor. But to create the Password Settings objects which go in that container, we could use ADSIedit, LDIFDE, or other tools. Once created, we could use those same tools to view and edit the settings, or we could come back to ADUC and use the Attribute Editor. In another article, we’ll see some PowerShell cmdlets in W2K8 R2 which offer an alternative.

Let’s look at a Password Settings object – the object class is msDS-PasswordSettings. Although these can be created in ADSIedit and then modified in ADUC, let’s see one in standard LDIF format.

dn: CN=Sales Password Policy,CN=Password Settings Container,CN=System,DC=777,DC=wernerconsulting,DC=com

objectClass: msDS-PasswordSettings

cn: Sales Password Policy

msDS-MaximumPasswordAge: -18144000000000

msDS-MinimumPasswordAge: -6048000000000

msDS-MinimumPasswordLength: 16

msDS-PasswordHistoryLength: 24

msDS-PasswordComplexityEnabled: TRUE

msDS-PasswordReversibleEncryptionEnabled: FALSE

msDS-LockoutObservationWindow: -6000000000

msDS-LockoutDuration: -18000000000

msDS-LockoutThreshold: 3

msDS-PasswordSettingsPrecedence: 10

Note that the raw format for the maximum password age, minimum password age, lockout observation window, and lockout duration is the classic Windows NT time interval “ticks”, which is a negative number representing the number of 100 nanosecond units in the duration. These are 64-bit values which are referred to as Integer8 (eight octets), or LargeInteger values, depending on if you ask a schema person or a developer.

When entering these values in ADSIedit, I’ve seen/heard people suggest that we use the ticks value for the time intervals, however, it is also possible to enter a value of (none), (never), or a duration in d:hh:mm:ss notation – days, hours, minutes, and seconds. A value of 0:00:10:00 represents 10 minutes. There really is no need to resort to ticks unless you prefer to count time that way.

Both ADUC’s Attribute Editor and ADSIedit support entering these values in d:hh:mm:ss notation, which automagically translates to the negative ticks notation required for time intervals.

In another article, we’ll look at the meaning of these settings, then later how to apply them to groups, and finally how to avoid the gory details of managing these in Windows Server 2008 and use PowerShell in Windows Server 2008 R2 for more fun and power.

-Brad

Related Courses

Automating Windows Server 2008 Administration with Windows Powershell (M6434)

Configuring, Managing, and Maintaining Server 2008 (M6419)

Configuring Windows Server 2008 Active Directory Domain Services (M6424, M6425)

Hi,

heute hat Microsoft das Kumulatives Zeitzonenupdate Dezember 2009 KB976098 für alle Microsoft Windows Betriebssysteme zur Verfügung gestellt!

Wichtig Dieses Update ersetzt, und ersetzt aktualisieren 970653, die wurde im August 2009 freigegeben. Dieses Update enthält außerdem zusätzliche Zeitzonenänderungen, die in nach Update 970653 erstellt wurde.
Wenn Sie bereits bereitgestellt haben 970653, aktualisieren, lesen die Beschreibungen der bestimmten Zeitzonenänderungen, die in diesem Artikel, um zu überprüfen, ob Sie dieses Update sofort bereitstellen müssen behoben werden. Wenn Systeme nicht direkt betroffen sind, können Sie die Bereitstellung bei der nächsten Gelegenheit einplanen.
Es wird empfohlen, dass Sie das aktuelle kumulative Zeitzonenupdate für Windows zu garantieren die Konsistenz der Zeitzonendatenbank auf allen Systemen bereitstellen.

Wichtig Bevor Sie das Update, das in diesem Artikel beschrieben wird anwenden, achten Sie potenzielle Probleme, die auf Microsoft Outlook auswirken können.
Weitere Informationen zu diesen Problemen finden Sie die folgende KB-Artikelnummer:

931667 (http://support.microsoft.com/kb/931667/ ) Wie Sie die Sommerzeitänderungen in 2007 mithilfe des Zeitzone Data Update-Tools für Microsoft Office Outlook

Wichtig

• Wenn Sie Microsoft Exchange Server in einer IT-Umgebung ausführen, müssen Sie zusätzliche Maßnahmen gewährleisten Sie den ordnungsgemäßen Betrieb von Exchange Server ausführen.
  Weitere Informationen zum Exchange Sommerzeit (DST) Update klicken Sie auf die folgende KB-Artikelnummer:

  941018 (http://support.microsoft.com/kb/941018/ ) Gewusst wie: Sommerzeit adressieren, mithilfe des Exchange Kalender-Update-Tools

• Kumulative Zeitzonenupdates enthalten nur Daten, die für eine bestimmte Region geändert hat oder, wurde hinzugefügt, um die Parität mit anderen Betriebssystemversionen beizubehalten. Daher, wenn ein Zeitzonenschlüssel gelöscht wurde, möglicherweise einige ursprüngliche Werte nicht wiederhergestellt werden nach der Installation des kumulativen Zone Updates.
  Wird nicht empfohlen, dass Sie alle Registrierungsschlüssel zu löschen, die sich auf Zeitzonen beziehen. Auf einem Computer, auf dem unvollständige Zeitzone Schlüssel verfügt, zuerst wiederherstellen Sie die Zeitzone Schlüssel aus einer als funktionierend bekannten Sicherung. Wenden Sie dann das Update.

Na dann, Viel Spass beim selber Testen!
CU

Buenas.

Hoy os muestro únicamente como instalar Windows Server 2008 R2 X64 versión standard en inglés y como prepararlo para poder usarlo en próximas ocasiones como base de otras instalaciones.

Lo voy a montar sobre un sistema con 2 GB de RAM, 2 CPU y con un disco C: de 15 GB. (Aunque no sea necesario disponer de tanta RAM ni de 2 CPU ni mucho menos para que este sistema operativo funcione, comentaros que he montado Windows Server 2008 con Domain Controller en un equipo con 384MB de RAM, sin usuarios conectados eso sí, pero el sistema funciona fluidamente. (Pero barbaridades las mínimas en entornos de producción) Ya sabéis, no derrochéis, pero en ningún caso quedaros cortos (mínimo 1 GB de RAM, y 15 GB de disco).

Espacio necesario en disco con instalación limpia + parches a día 21/11/2009.

A partir de ahora incluiré en mis próximos artículos una pantalla similar a la anterior para poder cuando lo deseéis consultar el tamaño necesario para una instalación limpia de un sistema operativo en un servidor con 2 GB de RAM, o con un Domain Controller, o con un Wsus, o con un Exchange, etc… (Digo lo de los 2 GB de RAM por que el sistema Windows Server 2008 actualmente administra automáticamente el nivel de memoria paginada y cuanta mas RAM tengamos en nuestro sistema mas necesario será disponer de espacio suficiente para albergar este archivo de paginación).

Empecemos con la instalación:

Lo primero que hay que hacer es disponer de una copia original del sistema operativo en cuestión, insertarlo en la unidad de CD y arrancar la máquina virtual, el servidor o lo que vosotros queráis.

Seleccionad en el campo Time and currency format: Spanish (Spain, International Sort) y pulsad sobre Next.

Pulsad sobre Install Now.

Seleccionad la versión del sistema operativo que queráis y pulsad sobre Next. En mi caso voy a instalar la versión Standard en versión Full Installation, NO en versión Core ya que necesito de un entorno gráfico para poderlo administrar de la forma que lo quiero hacer en esta ocasión. (Ya os explicaré en otro artículo las bondades del core).

Marcad I accpet the license terms y pulsad sobre Next.

Pulsad sobre Custom (advanced)

Seleccionad el disco donde lo queráis instalar y pulsad sobre Next.

Tras finalizar la instalación…

Pulsad sobre OK para crear la password del usuario administrador local. (Recordad que debe ser una contraseña segura, ya sabéis, números, letras, símbolos, mayúsculas, minúsculas)

Escribid la password y pulsad sobre

Pulsad sobre OK.

Al arrancar Windows Server 2008 siempre a no ser que marquéis la opción do not show this window at logon os aparecerá esta pantalla de bienvenida que por cierto es muy útil.

Ahora lo que vamos a hacer es un Windows Update para que esté al último nivel de parches del sistema operativo.

Pulsad sobre Download and install updates del apartado 2 Update This Server.

Pulsad sobre Turn on automatic updates.

Pulsad sobre Install updates.

Reiniciad el server.

Ahora que ya tenemos el servidor BASE concluido, vamos a prepararlo para que se pueda usar tantas veces como se quiera y no haya problemas de duplicidad de nombres, etc…

Nos ubicamos en Start –> Run–> y escribimos sysprep.

Nos aparecerá un explorador de Windows donde deberemos pulsar doble click sobre el fichero sysprep.

Marcad la opción Generalize y en el desplegable Shutdown Options seleccionad Shutdown y pulsad OK.

La opción Generalize provoca una eliminación del SID del equipo y de la configuración específica a nivel de software y hardware, también resetea el tiempo disponible antes de la activación del producto. Así podremos usar esta BASE para cualquier nueva implementación sin tener duplicidad de nombres de equipo ni problemas similares…

Saludos y hasta pronto MegaCracks.

Frequently while performing network assessments I need to assemble a list of all the programs installed on servers. Going to Add/Remove Programs and writing it down is a tedious process.  Installing applications like Belarc Advisor is a bit more intrusive then I want to be on another companies servers.  After some research today I found two solutions that work well:

For XP and Server 2003

http://www.billsway.com/vbspage/ShowScript.asp?tgt=txtfiles/InstalledPrograms.txt

The above contains the contents of a vbscript. You copy the contents into a text file and save it with a .vbs extension.  You can then double-click it. It will prompt you for a computer name or IP address. When it finishes running it generates a file that contains a list of all the programs installed.  It seems to work great with Windows XP and 2003, but only returns a partial list for Windows 2008. 

 For Vista, Windows 7, Server 2008 and 2008 R2

http://www.intowindows.com/how-to-get-list-of-installed-apps-in-vistawindows-7-without-any-software/

This link shows how to generate the list using wmi commands. It says it is for vista and windows 7, but seems to work on Server 2008 just fine. Unlike the vbscript, this must be run directly on the computer in question.

 Conclusion

Both these methods seem to work well, but they do generate files on the system that need to be copied off to be useful.  If you are using them on someone elses computers I would advise you get explicit permission before using these tool. 

Unrelated but also helpful.

If your assessment involves Dell servers, you might want to get the service tags for the servers.  Older Dells tend to put this sticker in inconvenient locations. Luckily you can query the servers for the tag using this handy vbscript.

http://lazynetworkadmin.com/content/view/13/6/

A Microsoft liberou uma coleção online composta por grupos de estudos que ensinam os usuários sobre os novos recursos e funcionalidades do Windows Server 2008.

Esta coleção inclui a virtualização de servidores, segurança e gerenciamento de políticas, gestão de filiais, acesso a aplicações centralizadas, e gerenciamento de servidores. Além da coleção ser composta de uma rica experiência multimídia.

Ela é destinada a profissionais de TI que estão interessados em novos recursos e funcionalidades do Windows Server 2008.

Para tirar o máximo proveito desta coleção é recomendado que você tenha experiência na implementação do Windows Server 2000 ou Windows Server 2003 e também entenda inglês.

O link é: https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=216481

If you don’t mind an estimated 2% performance hit, try it this way next time.  Click here to learn about .VHD.

Hi,

heute morgen hieß es für mich früh austehen, 5:15 Uhr klingelte der Wecker, denn um 06:28 Uhr fuhr mein IC nach Hannover, wo ich planmassig ankam und mit der S5 weiter zum Hannover Flughafen fahren konnte. Hier fand im Maritim Airport Hotel die Microsoft Windows 7 Joint Launch Roadshow statt.

Nach kurzer Registrierung und einem Tee hielt Michael Kalbe die Keynote „Effizienz, neu definiert“.

• Kosteneinsparung
• Cloud Computing
• ….

Weiter ging es für mich in Track 3 zu Microsoft Exchange Server 2010 – Die technischen Neuerungen im Detail (Sprecher: Malte Pabst)

• Hub Transport ausgebaut und mit weiteren Policy Funktionen
• MAPI Client Zugriff über CAS-Server, CAS-Server spricht mit Mailbox-Server
• UM Server, integriert SMS in Exchange (Windows Mobile 6.5 nötig), SMS wird dann über Active Sync an WM Geräte übergeben und vom Client Gerät versendet
• Mailbox Archivierung direkt im Postfach (extra Archiv pro User)
• Native Verbindung/Koexistenz von Exchange Online Service mit Exchange On-Premise im eigenen Unternehmen (SPAM, Archiv, …)
• Veränderte Storage Situation, Support für Direct Attached SATA Disks und JBOD SATA (RAID-Less)
• DAG – Database Availibility Group
  • Ab 2 Server
  • Windows Server 208 R2 Enterprise (Failover Cluster Funktion), für CAS reicht Server 2008 Std (NLB)
  • Exchange Std (5 Mailbox DB´s) oder Enterprise (100 Mailbox DB´s)
  • Log File Shipping
  • Passive Kopie der MBX DB auf anderen DAG Cluster knoten
  • Sinnvolle Lastverteilung zwischen DAG Cluster Knoten
  • Ausstattung der Server sollte ähnlich sein, muss aber nicht
  • Identische Laufwerkszuordnung sinnvoll
  • Für Öffentliche Ordner kein DAG Support, Replikation der Public Folder
  • PowerShell v2 nötig, Remote PowerShell Support
• Exchange Control Panel
  • Durchführung von Administrationsaufgaben per Browser
  • Delegierung (User, Empfänger Verwaltung)
  • kein ActiveX, Firefox, Safari, … Support
  • Selfservice für Verteilergruppen und Kontaktinformationen
  • Nachrichtenverfolgung für Benutzer
• Exchange Federation
  • Teilen von Kalenderinformationen mit Partnern
  • Rights Management
  • Message Tracking
  • Microsoft Federation Gateway (MFG)
• Integration von UC in Outlook Web App (OWA)
• Clients
  • Outlook 2010, Mailtip, dass Mail zu gross, dass Mail an Verteilerliste gesendet wird
  • Konversationsansicht, egal welche Nachrichtenform
  • Outlook Web App, Tread-View, keine ActiveX -> Firefox, Safari Support
• Verteilerlisten
  • Content Approval Support, Message Moderation

Exchange 2010 Von Architektur und Design zu Deployment und Migration (Sprecher: Malte Pabst)

• Windows Server 2003 DCs/GCs ab SP2 in jeder AD Site
• Forest Level und Domain Level Windows Server 2003
• Alle Exchange 2003 Service SP2/Exchange 2007 SP2
• Exchange 2007 Koexistenz Support ab E2k7 SP2
• Serverplanung
  • Mit nur einer Rolle max 12. Cores
  • Server mit mehreren Rollen max. 24 Cores
  • CAS:Mailbox 3:4
  • Hub:Mailbox 1:7 (ohne AV auf Hub), sonst 1:5
  • GC: Mailbox 1:4 (32 bit), 1:8 (64 bit)
  • 4-12 Cores für MBX Server, 4 GM RAM + 2-10 MB pro User Mailbox (32 MB – 64 GB)
  • Disk/Storage Calculator für Disk Planung (89 KB – 250 KB pro Mail)
  • CAS Server, mind 8 GB bzw. 2 GB pro Core (gestiegenen Anforderungen durch MAPI Traffic), 4-12 Cores
  • Hub Transport 4-8 GB (4-12 Cores)
  • MBX, CAS, Hub, min. 8 GB RAM +
• Deployment Assistent online oder als PDF
• Exchange 2010 Profile Analayzer 2010 (EPA) zur Zeit noch Beta
• Validierung vor Live Betrieb mit Jetstress 2010 oder Exchange Load Generator 2010 (Achtung NICHT in Produktiv Umgebung einsetzen, da Extra User angelegt werden, Lastsimulation)
• Virtualisierung
  • Planung der Hostsysteme ebenso wichtig
  • Planung der Gäste sollte ähnlich der physischen Exchange Anforderungen sein
  • Performanceverlust bis zu ca. 12 %
  • Host Server 2008 / R2 Hyper-V
  • Gast Windows Server 2008 R2 für virtuelles Exchange 2010 (PowerShell V2), UM keine Virtualisierung
  • Fixed Disk für Exchange Gast Systeme, Pass-Throught für MBX Systeme (iSCSI, …)
• CAS, Hub, UM, MBX Server
• Management von 2010 Exchange Servern nur mit Exchange 2010 Tools, 2007 Exchange Server nur mit 2007 Tools und 2003 Exchange Server mit Exchange 2003 Tools

Exchange 2010 Compliance bzw. rechtssichere Kommunikation (Sprecher: Malte Pabst)

• “Paperwork” -> Gesetze studieren, Regeln definieren und vermitteln
• Persönliches Online Archiv pro User
  • in der gleichen MBX DB (default 10 GB)
  • kann Offline mitgenommen werden in Outlook (nur Outlook 2010/Outlook Web App 2010),
  • PSTs können direkt eingebunden/importiert werden
  • Anwendung von Richtlinien möglich (verschieben der Mails automatisch aus Inbox in Archiv)
  • Exchange 2010 Enterprise CAL nötig

• Definieren von Aufbewahrungsregln
• Suche über mehrere Postfächer, Multi-Mailbox Suche, delegiert auf Personenkreis
• Journaling, mit erweiterten Funktionen für Überwachung, Auswertung und Kontrolle
  • Basieren auf Exchange Hub Transport Regeln
  • Regelbasierende Aufzeichnung von Nachrichten
  • Integration von RMS
  • Berichtswesen
  • Ablage aus ausserhalb der Exchange Org (Weiterleitung per SMTP, Ablage auf WORM Medien)

• Überwachung und Auswertung
• Transport Regeln, Vorgabe von Regeln auf Hub Transport Server
  • Filtereinstellungen (Absender, Empfänger)
  • Disclaimer
  • Erstellen von Kopien (an, cc, bcc)
  • Manipulation des Mailheaders
  • Integration von Sicherheitsvorlagen (RMS)
  • Annahme verweigern
  • Ausnahmen definieren (Abarbeitung ähnliche FW Regeln)
• Outlook Regeln, können offline mitgenommen werden
  • Verknüpft Informationen im Outlook mit RMS Vorlagen
  • Integration in AD RMS
  • Zentral verwaltet über Exchange Org
  • PowerShell Zuweisung
• Transport Verschlüsselung (TLS)
• Enhanced Transport Conditions
• Moderation (Verteilerlisten)
• Mail Tips

PowerShell v2 Umfassende Automation der Serververwaltung (Tobias Weltner)

• Effizienz und Skalierung
• PowerShell v1 wird von v2 ersetzt
• Cmdlets und parameter
• Support für PowerShell Remoting (Windows Management), erfordert Windows Server 2008 R2/Windows 7 oder Active Directory Gatway Services zur Umwandlung von DCOM in XML

Microsoft Forefront Integrierte Sicherheit zum Schutz von Client, Server und Netzwerk (Daniel Melanchthon)

• Derzeit:
  • Forefront Client Security für Endpoint Security (Server & Client)
  • ISA2006 + IAG 2007 für  Edge Security
  • sowie Forefront Security für Exchange, SharePoint und OCS, sowie Forefront Online Protection für Exchange

• Forefront Client Security 1 Engine (Microsoft)
• Forefront Server Produkte bis 5 Engines nutzbar (Microsoft, Kaspersky, …)
• Planung:
  • sowie Forefront Security für Exchange und sowie Forefront Online Protection für Exchange ist verfügbar, SharePoint in Planung Anfang 2010
  • Profront Protection Manager (zentrale Mgmt Tool) in Planung Anfang 2010
  • TMG 2010 ist verfügbar UAG Anfang 2010 für Edge Security
  • Forefront Endpoint Security in Planung für 2. Halbjahr 2010

Hier noch ein paar Impressionen der Microsoft Windows 7 Joint Launch Roadshow:

Vollständiges Album anzeigen

Na dann, Viel Spass beim selber Testen!
CU

Citrix learning is providing new training for Citrix Essentials for Hyper-V. Go and catch your seat.

Description

This course is available at no cost for a limited time only!  Register now to add this course to your learning transcript and lock in the promotional offer. This course will remain available in your learning transcript for future access. Note: New users will need to create an account.

In this Essentials for Hyper-V online training course, learners will be introduced to Citrix Essentials for Hyper-V and gain the knowledge needed to perform basic installation and configuration tasks. Through online simulations, students will install and configure key features and explore product capabilities, such as virtual storage management, provisioning services, lifecycle management and workflow studio.

New content added!
This course is now updated to include features and enhancements aligned with the Windows Server 2008 R2 release.

Register

Механизм активации Windows 7 был взломан ещё до официального выхода этой ОС. Однако, предложенный метод требовал изменений в BIOS, что является весьма нетривиальной задачей.

Сейчас хакеры нашли вариант полного обхода механизма Windows Activation Technologies (WAT) без манипуляций с BIOS’ом и вообще без использования ключа активации.

С помощью этого метода блокируется работа модулей SPP (Software Protection Platform) и SLC (Software Licensing Client). И хотя 30-дневный счётчик периода активации может продолжать видимость работы, он уже не инициирует никаких действий. Для блокировки используются следующие команды:

takeown /F %WINDIR%\System32\sppcomapi.dll

icacls %WINDIR%\System32\sppcomapi.dll /deny *S-1-1-0:F

Здесь sppcomapi.dll — библиотека, с помощью которой контролируется основная часть функций SPP. Данным метод можно применять для операционных систем Windows 7 и Windows Server 2008 R2.

С целью автоматизации процесса блокировки активации хакеры создали программы RemoveWAT и Chew-WGA .

По заявлению представителей Microsoft, они в курсе проблемы и уже занимаются ее решением. В Microsoft также подчеркнули важность использования лицензионного ПО.

Windows Server 2008 R2 Overview

July 22, 2009 – This afternoon, Microsoft announced that it has finished the development work on Windows Server 2008 R2. The company released gold code to manufacturing, which means that customers, partners, OEMs and subscribers to TechNet and MSDN services will receive the code over the coming few weeks.

Windows Server 2008 R2, builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new features to enable IT professionals to increase the reliability and flexibility of their server infrastructures. New virtualization tools, Web resources, management enhancements, and exciting Windows 7 integration help save time, reduce costs, and provide a platform for a dynamic and efficiently managed data center. Powerful tools such as Internet Information Services (IIS) version 7.0, updated Server Manager and Hyper-V™ platforms and Windows PowerShell version 2.0 combine to give customers greater control, increased efficiency and the ability to react to front-line business needs faster than ever before.

The key technology investments in Windows Server 2008 R2 include:

Virtualization. With its server virtualization technology, Windows Server 2008 R2 enables you to reduce costs, increase hardware utilization, optimize your infrastructure, and improve server availability.

Management. Windows Server 2008 R2 reduces the amount of effort you expend managing your physical and virtual data centers by providing enhanced management consoles and automation for repetitive day-to-day administrative tasks.

Web. Windows Server 2008 R2 gives you the ability to deliver rich Web-based experiences efficiently and effectively, with improved administration and diagnostics, development and application tools, and lower infrastructure costs.

Scalability and Reliability. With enterprise IT departments shouldering ever-heavier burdens, Windows Server 2008 R2 has been designed specifically with heavier workloads for both across server and client computing. On the server side, R2 includes architectural enhancements for more compute power and role componentization as well as specific features enhancing reliability and security.

Better Together With Windows 7. Windows Server 2008 R2 includes technology improvements designed with Windows 7 enterprise users in mind, augmenting the network experience, security and manageability.

As you read each section, you can identify which Windows Server 2008 R2 features and capabilities will help you create solutions for your organization. You can also see how Windows Server 2008 R2 can help you manage and protect your existing solutions.

You can buy Windows Server Software in Microsoft Store