Tag: Windows XP

Hoe Office 2007 distribueren met MDT

1. “Deployment Workbench” > “Distribution Share” > “Applications” > “New”.

2. Kies voor “Application with source files”.

3. Vul de gegevens in:

image

4. Geef de locatie van de bestanden op. In mijn geval was dit de Office 2007 DVD.

image

5. Hoe moet de map heten.

image

6. Geef bij command line setup.exe in:

image

7. Finish & en hij gaat het zaakje kopieeren
image

8. Als je de properties kiest van Office 2007 Enterprise
image
9. Dan zie je dat er een tabblad is bijgekomen genaamd Office Products

image

10. Nu kunnen we deze gaan aanpassen:
image  

Display level: None betekent silent install

Vergeet niet om even op Apply te klikken. Nu wordt er een xml op de achtergrond aangemaakt.

11. Als je op Apply geklikt heb ga dan terug naar het tabblad Details.

Je ziet nu dat quint install command is aangepast naar: setup.exe /config Enterprise.WW\config.xml

12. Ga weer net tabblad Office Products

13. Wanneer je Office Customization Tool aanklikt dan krijg je het volgende te zien.
Je kunt dus alles aanpassen wat je wilt.
image

14. Als je nu op Edit config.xml doet krijg je het volgende te zien.
image

Ik heb de config even aan moeten passen zodat deze werkt aangezien ik de NL versie distribueer.

<Configuration Product="Enterprise">
  <Display Level="none" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" />
  <Logging Type="standard" Path="c:\" Template="Microsoft Office Enterprise Setup(*).txt" />
  <PIDKEY Value="XXXXXXXXXXXXXXXXXXXXXXXXX" />
  <Setting Id="Reboot" Value="IfNeeded" />
</Configuration>

15. Als je het volgende in config.xml aanpast met het volgende dan wordt alleen Word, Excel, Powerpoint & Outlook geinstalleerd. ‘

   <OptionState Id="ACCESSFiles" State="Absent" /> //access
  <OptionState Id="WordFiles" State="Local" Children="force" /> //Word
  <OptionState Id="ExcelFiles" State="Local" Children="force" /> //Excel
  <OptionState Id="OUTLOOKFiles" State="Local" Children="force" /> //outlook
  <OptionState Id="PPTFiles" State="Local" Children="force" /> //Powerpoint
  <OptionState Id="PubPrimary" State="Absent" /> //publisher
  <OptionState Id="RMSFiles" State="Absent" /> //Interconnect
  <OptionState Id="XDOCSFiles" State="Absent" /> //infopath
  <OptionState Id="GrooveFiles" State="Absent" /> //groove
  <OptionState Id="OneNoteFiles" State="Absent"  /> //onenote
  <OptionState Id="SHAREDFiles" State="Absent"  /> //onenote
  <OptionState Id="ToolsFiles" State="Absent"  /> //onenote
  <OptionState Id="CAGFiles" State="Absent" /> //Clip Organizer
  <OptionState Id="DocServicesFiles" State="Local" Children="force" /> //docu update util
  <OptionState Id="HTMLSourceEditing" State="Local" Children="force" /> //script editor
  <OptionState Id="DocumentImagingUtils" State="Local" Children="force" /> //scanning,ocr,indexing
  <OptionState Id="OISFiles" State="Absent" /> //picture manager
  <OptionState Id="OSESupp" State="Absent"  /> //sharepoint support
  <OptionState Id="QueryFiles" State="Absent" /> //msQuery
  <OptionState Id="VisioPreviewerFiles" State="Local" /> //visio viewer
  <OptionState Id="RefIEBarFiles" State="Absent" /> //research explorer bar
  <OptionState Id="WebDriveFiles" State="Absent"  /> //hosted webs
  <OptionState Id="VBAFiles" State="Absent" /> //VB for applications
  <OptionState Id="OfficeDigitalSFiles" State="absent" /> //vba certificates

Office 2007 aan een task toevoegen.

1.  Deployment Workbench > Task Sequences > Windows XP > Properties.

2. Ga naar tabblad Task Sequence
image 

3. Ga naar State Restore > Install Applications. Kies Install a single application > Microsoft Office 2007 Enterprise. en klik op OK.

Windows 2008 R2, Hyper V2, Exchange 2010, MDT Video’s

Op Edge van Microsoft Technet staan een heleboel mooie Video’s gemaakt door Microsoft.

Heb er maar even een mooie verzameling van gemaakt.

Zoals normaal je heb je geen “tijd” om alles te lezen of je moet geen leven hebben

Als je iets zit wat je leukt wat er bij zit vindt doe je voordeel er mee.

Windows Server 2008 R2: Remote Desktop Services – The Series (P1)
Windows Server 2008 R2: Remote Desktop Services – The Series (P2)
Windows Server 2008 R2- Remote Desktop Services – The Series (P3)
Windows Server 2008 R2- Remote Desktop Services – The Series (P4)
Windows Server 2008 R2- Remote Desktop Services – The Series (P5)

Part 1 Master Your Environment with System Center Configuration Manager 2007
Part 2 Master Your Environment with System Center Configuration Manager 2007
Part 3 Master Your Environment with System Center Configuration Manager 2007
Part 4 Master Your Environment with System Center Configuration Manager 2007

Hyper-V R2- Failover & Live Migration
Hyper-V R2- Making Highly Available VMs
Hyper-V R2- Making Highly Available VMs
Hyper-V R2- Dynamic Storage
Hyper-V R2- USB over Network with Fabulatech
Hyper-V R2- Introducing Cluster Shared Volumes
Hyper-V R2- Building a Hyper-V R2 Cluster
Hyper-V R2- Initial Installation & Configuration

Demo 1 – Hyper-V Live Migration
Demo 2 – Boot From VHD
Demo 3 – Windows PowerShell 2.0 Remoting
Demo 4 – Active Directory Enhancements

Microsoft Deployment Toolkit – building install media for Windows 7
Windows XP Migration to Windows 7 RC using MDT Beta 1 – Part 1- The OS Install
Windows XP Migration to Windows 7 RC using MDT 2010 Beta 1 – Part 2- How To Build It…

Open Source Software (OSS) on Windows Server 2008

Exchange 2010 Demo: Read and Reply State
Exchange 2010 Demo: Conversation View
Exchange 2010 Demo: Move Conversation
Exchange 2010 Demo: Nickname Cache
Exchange 2010 Demo: UM Card

Interview with Kristian Andaker on Transitions to Exchange Server 2010
Interview with Kristian Andaker on Exchange 2010 OWA
Interview with Matt Gossage on Exchange Server 2010 and Storage
Interview with Scott Schnoll on Exchange 2010 High Availability
Interview with Scott Schnoll on Backup Strategy in Exchange 2010
Interview with Becky Benfield on Exchange 2010 Site Resiliency at Tech Ed 2009

Waarom zijn dagen zo kort!!!!!!!!!!!!!

VMware Server 2.0.1

VMware heeft buildnummer 156745 van zijn virtualisatie software Server 2.0.1 uitgebracht. Dit pakket doet zijn werk onder Linux en Windows en is in staat om via een virtuele machine diverse besturingssystemen op de hostcomputer te laten draaien. Voor de gast computer kan je gebruikmaken van verschillende BSD-varianten, diverse Linux-distributies, Solaris en Windows. Voor meer informatie verwijzen we jullie door naar deze pagina en deze handleiding in pdf-formaat. De lijst met veranderingen voor versie 2.0.1 ziet er als volgt uit:

What’s New
Server 2.0.1 is a maintenance release that resolves security as well as some known issues. With this release of VMware Server, certain new features and support have been added.
Support for New Guest Operating Systems
VMware provides support for the following operating systems for Server 2.0.1:

  • Asianux Server 3.0 Service Pack 1
  • CentoOS 4.7
  • CentOS 5.2
  • Windows Essential Business Server (EBS) and Small Business Server (SBS) 2008
  • Windows Small Business Server 2003 Service Pack 2
  • Windows XP Service Pack 3
  • Windows Vista Service Pack 1

Security Fixes:

  • VMnc codec heap overflow vulnerabilities
    The VMnc codec assists in record and replay of sessions which are records of the dynamic virtual machine state over a period of time. Two heap overflow vulnerabilities might allow a remote attacker to execute arbitrary code on VMware hosted products. For an attack to be successful, the user must visit a malicious Web page or open a malicious video file. The Common Vulnerabilities and Exposures project has assigned the names CVE-2009-0909 and CVE-2009-0910 to these issues.
  • A VMCI privilege escalation on Windows-based hosts or Windows-based guests
    The Virtual Machine Communication Interface (VMCI) provides fast and efficient communication between two or more virtual machines on the same host and between a virtual machine and the host operating system. A vulnerability in vmci.sys might allow privilege escalation on Windows-based machines. This might occur on Windows-based hosts or inside Windows-based guest operating systems. Current versions of ESX Server do not support the VMCI interface and hence they are not affected by this vulnerability. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1147 to this issue.
  • A remote denial-of-service vulnerability in authd for Windows-based hosts
    A vulnerability in vmware-authd.exe might cause a denial-of-service condition on Windows hosts. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-0177 to this issue.
  • Updated vm-support script
    This release improves data collection when the vm-support script is run by the Server administrator on request of VMware support or its support partners. The file that contains the SSL keys for communication between Server and vCenter and other applications is no longer collected. For more details, see the KB article Data Security Best Practices – SSL keys for communicating with VirtualCenter and other applications (KB 1008166).
  • Windows-based host privilege escalation in hcmon.sys
    A vulnerability in an I/O Control (ioctl) function in hcmon.sys might be used to escalate privileges on a Windows-based host. The Common Vulnerabilities and Exposures project has assigned the name CVE-2009-1146 to this issue. New releases of hosted products address a denial-of-service problem described in CVE-2008-3761, which can only be exploited by a privileged Windows account.
  • Denial-of -service vulnerability in a virtual device
    A vulnerability in a guest virtual device driver might allow a guest operating system to cause the host and consequently any virtual machine on that host to fail. The Common Vulnerabilities and Exposures project has assigned the name CVE-2008-4916 to this issue.

Miscellaneous Fixes:

  • Mount installer option mounts current CD-ROM image instead of VMware Tools installer image
    If a CD-ROM image is mounted to a virtual machine with VMware Tools installed, the Mount installer option in the Web UI incorrectly mounts the CD-ROM image instead of the VMware Tools image. The issue is resolved in this release.
  • Unable to install the latest version of VIX API on Server 2.0.x
    You cannot install VMware VIX API 1.6.2 of due to an issue with the MSI installer for VIX API. This issue is resolved in this release.
  • The default VI Web Access HTTP connection port is 8222 and the default HTTPS port is 8333. If you use these defaults, or any values other than 80 (HTTP) and 443 (HTTPS), you must specify the port number when you connect to VMware Server using VI Web Access. You must also allow connection to these ports through your firewall. An example URL to connect to VI Web Access is http://server_host:8222 If you want to use ports 80 (HTTP) and 443 (HTTPS), override the default values during installation. Note: If you are running IIS or Apache web server on the default ports, specify alternate HTTP and HTTP ports when prompted by the Windows installer or vmware-config.pl. Alternatively, stop IIS’s default Web site or any other Web site running on these ports. On Linux, shut down Apache or any other application using these ports and make sure they are not configured to restart automatically. This issue is resolved in this release.

VMware heeft ESX(i) 3.5 U4 Vrijgegeven

VMware heeft update 4 vrijgegeven. Release info bekijk het HIER.

Bekijk zeker de  compatability matrix, ESX(i) 3.5 U4 vereist vCenter 2.5 U2 of hoger.

Nieuwe ondersteunende Functies

Nieuw ondersteunde Operating Systems:

  • SUSE Linux Enterprise Server 11 (32-bit and 64-bit).
  • SUSE Linux Enterprise Desktop 11 (32-bit and 64-bit).
  • Ubuntu 8.10 Desktop Edition and Server Edition (32-bit and 64-bit).
  • Windows Preinstallation Environment 2.0 (32-bit and 64-bit).

Nieuwe ondersteunde SAS/SATA controllers:

  • PMC 8011 (for SAS and SATA drives)
  • Intel ICH9
  • Intel ICH10
  • CERC 6/I SATA/SAS Integrated RAID Controller (for SAS and SATA drivers)
  • HP Smart Array P700m Controller

Expanded support for the Enhanced VMXNET driver :

  • Microsoft Windows Server 2003, Standard Edition (32-bit)
  • Microsoft Windows Server 2003, Standard Edition (64-bit)
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Small Business Server 2003
  • Microsoft Windows XP Professional (32-bit)

Set Hardware Acceleration Level

Ik vond een mooi script op het Edugeek. Het zet automatisch Hardware Acceleration Level op full.

Const HKEY_LOCAL_MACHINE = &H80000002
sComputer = "."
sMethod = "GetStringValue"
hTree = HKEY_LOCAL_MACHINE
sKey = "HARDWAREDEVICEMAPVIDEO"
sValue = "DeviceVideo0"
Set oRegistry = GetObject("winmgmts:{impersonationLevel=impersonate}//" & sComputer & "/root/default:StdRegProv")
Set oMethod = oRegistry.Methods_(sMethod)
Set oInParam = oMethod.inParameters.SpawnInstance_()
oInParam.hDefKey = hTree
oInParam.sSubKeyName = sKey
oInParam.sValueName = sValue
Set oOutParam = oRegistry.ExecMethod_(sMethod, oInParam)
strParse = oOutParam.Properties_("sValue")
sMethod = "SetDWordValue"
hTree = HKEY_LOCAL_MACHINE
sKey = Replace(strParse, "RegistryMachine", "")
sValueName = "Acceleration.Level"
‘* In Windows XP Change the uValue value for Accelleration.Level from 0 (FULL) to 5 (none)
uValue = 1
Set oRegistry = GetObject("winmgmts:{impersonationLevel=impersonate}//" & sComputer & "/root/default:StdRegProv")
Set oMethod = oRegistry.Methods_(sMethod)
Set oInParam = oMethod.inParameters.SpawnInstance_()
oInParam.hDefKey = hTree
oInParam.sSubKeyName = sKey
oInParam.sValueName = sValueName
oInParam.uValue = uValue
Set oOutParam = oRegistry.ExecMethod_(sMethod, oInParam)
sComputer = Empty
sMethod = Empty
hTree = Empty
sKey = Empty
sValue = Empty
sValueName = Empty
uValue = Empty
Set oRegistry = Nothing
Set oMethod = Nothing
Set oInParam = Nothing
Set oOutParam = Nothing
WScript.Quit

Sla het bovengenoemde script op als een vbs.
Je kunt dit ideaal gebruiken tijdens het deployen van virtuele machines via MDT in combinatie met automatische uitrol van VMware Tools. Nu hoef je zelf niet meer de Hardware Acceleration level aan te passen. Ik heb het getest onder XP & Windows 2003.

Outlook 2007 Anywhere Exchange 2007

1. Klik in het menu Extra op Accountinstellingen, selecteer het Exchange-account en klik vervolgens op Wijzigen.

2. Klik op Meer instellingen en klik vervolgens op het tabblad Verbinding.

3. Schakel onder Outlook Anywhere het selectievakje Via HTTP verbinding maken met Microsoft Exchange in.

clip_image002

Opmerking: Als de sectie Outlook Anywhere niet beschikbaar is, is Windows XP Service Pack 2 of hoger vermoedelijk niet op de computer geïnstalleerd.

4. Als u een proxyserver wilt opgeven, klikt u op Proxy-instellingen van Exchange.

clip_image004

1 Voer bij url in je domein naam in waarmee je vanaf buiten kunt connecten naar de exchange server.

2.  Als je een SSL verbinding wilt gebruiken vinkje aan Alleen verbinden via SSL in.

5. Klik onder Instellingen voor proxyverificatie op Basisverificatie of NTLM-verificatie, NTLM-Verificatie wordt standaard gebruikt die uitleg hieronder.

clip_image006

Opmerking: Bij het gebruik van Basisverificatie wordt het wachtwoord in de vorm van leesbare tekst verzonden. Voor de beste beveiliging wordt geadviseerd de opties NTLM-verificatie en Alleen verbinden via SSL in te schakelen.

Windows Deployment Toolkit 2008 (MDT) testen VMWare Workstation

Maak een Virtuele Machine aan OS Windows XP.
Zorg dat deze een Disk heeft van 10GB en 512MB geheugen lager als 512MB dan werkt MDT niet.
Voeg in de VMX file de volgende regel toe dan heb geen vmware drivers nodig
ethernet0.VirtualDev = “e1000”
Start de VM en boot van netwerk met PXE en druk dan twee keer op F12.

clip_image002
clip_image004

clip_image006

Voor nu laat ik het hierbij. Er komt nog een vervolg hier op met de deployen van Windows SP3 op de meest makkelijk en ideale manier.

Beschrijving van de Windows Server 2008 read-only domain controller compatibility pack voor Windows Server 2003 en voor Windows XP

Deze update oplost sommige problemen die optreden met clients die functies van Windows Server 2008 RODC niet ondersteunen.

http://support.microsoft.com/?id=944043

IE7 “The publisher could not be verified” while running executable from network

Ik had een probleem bij een klant waarop een xp pc de volgende melding verscheen:
Publisher Could Not Be Verified
Publisher Could Not Be Verified

 Oplossing:

When you are trying to run an executable located on another machine on your network, running Windows XP SP2 or higher, you are accosted with a prompt: “The publisher could not be verified”. You are forced to confirm that you wish to run this program… every time you run it.

You can disappear this message by setting the following Group Policy Object (GPO)

Go to User Configuration >> Administrative Templates >> Windows Components >> Attachement Manager and add “*.exe” to the “Inclusion list for moderate risk file types” setting.

“This policy setting allows you to configure the list of moderate risk file types. If the attachment is in the list of moderate risk file types and is from the restricted or Internet zone, Windows prompts the user before accessing the file. …”

In other words, this allows you to run an .exe from the Intranet zone without a prompt, but it will warn before running one from the Internet. A lot of people are instructing to add *.exe to the list of low-risk file types. Doing so, you are allowing .exe files to execute from anywhere on the internet.

 

Translate »