Wanneer u hebt De ZijUitbreidingen van de Cliënt van de Voorkeur van het Beleid van de groep (GPP) (CSE) gedownload zult u opmerken dat zij niet (nog) in zijn .MSI formaat dat - zo gebruikt De Installatie van de Software van het Beleid van de groep (GPSI) is niet mogelijk. Bummer, recht!?

Wij hebben .EXE dossiers voor Vensters XP/2003 en .MSU dossiers voor het Uitzicht van Vensters… Maar dat is niet het enige ding dat wij hebben moeten om denken over. Vóór „het opstellen van“ deze dingen aan de cliënten op het netwerk dat wij hebben moeten om OS kennen versie (XP/2003/Vista), OS architectuur (32 of met 64 bits), Het Niveau van het Pak van de dienst, en al dan niet de Voorkeur van het Beleid van de Groep Eerste vereisten (WmlLite - http://support.microsoft.com/kb/914783/en-us) zijn geïnstalleerde.

Om al dit vrij gemakkelijk te maken heb ik een „manifestatie“ gecre�ërd manuscript voor het opstellen van GPP CSEs gebruikend StartManuscript een - of handlancering (in admincontext). Mijn goede vriend Jeremy Moskowitz gevraagd me om dit te doen - zo, een paar uren later de „manifestatie“ - of“bèta„- het manuscript is openbaar (download hieronder)…

Nota: Ik heb niet in alle scenario's, maar I kunnen nog testen *denk* zij zijn vrij goed behandeld allen onderhand. Gelieve te rapporteren terug als u om het even welke problemen - om het even welk vindt koppel terug is welkom!

If you have ever tried defining the Security Options policy setting called: "Interactive logon: Message text for users attempting to log on", you may have had some difficulties formatting the message the way you wanted it. This blog is about "how to" workaround a minor bug in the GPEDIT tool…

The issue:

First things first - the Group Policy setting is located here:

"Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\"

The value is a Multi-String registry value that allows you to make multiple lines in the message. The message pops up right after a users hits Ctrl+Alt+Del as a general warning to the user before actually logging on. But, unfortunately the formatting isn’t as perfect as it could be.

What happens is, that carriage returns are lost after formatting this "pre-logon message" with GPEDIT, imagine you would want a message like this (see Figure 3):

—>

I don’t know why this should be so hard? Jump next line please…

Let’s do a comma, and continue the line…
Line number

…

After Internet Explorer Maintenance Group Policy settings are configured in a domain, a 20-second delay occurs when you log on to the domain from a client computer that has Internet Explorer 7 installed

SYMPTOMS
In an Active Directory directory service domain environment, you configure the Internet Explorer Maintenance Group Policy settings. A user logs on to the domain from a Windows XP-based, or a Windows Server 2003-based client computer that has Internet Explorer 7 installed. However, the user experiences a 20-second logon delay compared with a client computer that has Internet Explorer 6 installed.

To verify this delay, you can view the contents of the Branding log file (Brndlog.txt) for Internet Explorer Maintenance.

Note The Brndlog.txt file is in the following folder:
%UserProfile%\Local Settings\Application Data\Microsoft\Internet Explorer

In the Branding log file, you may see the information that resembles the following:

10/25/2007 10:36:37 Refreshing browser settings…
10/25/2007 10:36:37 Broadcasting “Windows settings change” to all top level windows…
10/25/2007 10:36:57 Done.

This sample shows that a 20-second delay occurs in the following phase: Broadcasting “Windows settings change” to all top level windows

CAUSE
Internet Explorer 7 introduced an error that causes this problem. This…

This tutorial assumes that you’re running Windows Deployment Services and want to update the default BOOT.WIM file to enhance platform compatibility, but the processes for injecting extra drivers into a WIM file are exactly the same for ANY WIM-based image.

You’ll need a full install of the WAIK, as it contains the necessary tools to manage WIM files. This can be done on any system, but if you’re running WDS it will install properly on the WDS server. Insert the DVD and select “Windows AIK Setup� and install WAIK.

Next you’ll need to create a folder to easily modify BOOT.WIM. I found it easiest to create a Temp folder, and then two more folders within that called Mount and Drivers. Then copy BOOT.WIM from the Vista DVD to the TEMP folder and rename it CUSTOMBOOT.WIM.

Now download the drivers you need, and extract them to \Temp\Drivers.

You’re not after DOS drivers – remember that this is Windows PE 2.0 so XP drivers are the best ones to use (or Windows Vista, if they’re available).

WinRAR is a great tool for extracting the contents of an EXE while maintaining…