Jump to content

chontay

Member
  • Posts

    2
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About chontay

chontay's Achievements

0

Reputation

  1. Hi All I am being driven slowly mad by this!!! I have the latest WAIK installed. I have WDS installed on 2003 Srv in Mixed mode. I have a Windows 7 Pro image on the WDS. I have WDS configured to Auto name the machines using name%# (this works perfectly for the WindowsXP images). It is also configured to place the created accounts in a specific OU which also works for XP. Windows 7 however is being a complete nightmare to unattend install. It joins the domain but creates an aut generated named account. It sets everything to US settings and it doesn't place the accounts in the correct OU. The relevant portions of my .xml are as follows: <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <InputLocale>en-GB</InputLocale> <UserLocale>en-GB</UserLocale> <UILanguage>en-US</UILanguage> <SystemLocale>en-GB</SystemLocale> <UILanguageFallback>en-GB</UILanguageFallback> I have tried en-UK and 0809:00000809 <ComputerName>%MACHINENAME%</ComputerName> <MachineObjectOU>domain.local/WDS</MachineObjectOU> Once the machine is built it will work fine but has the wrong name and region and OU. I've spent weeks on and off on this. Can someone please tell me once and for all how exactly I get this right. I can't see where i'm going wrong and have no decent help on the various searches and forums out there. Thanks in advance Rob
  2. Hi All New to the site so pleased to meet you. I have been deploying Office 2003 Pro via a group policy and a central admin share for years. When SP1 & 2 came out I slipstreamed it into the install share and it rolled out just as perfectly as before. But since SP3 released I have been unable to get the app to deploy. I slipstreamed SP3 into the install and it just fails every time! The logs report the installation source is not available but this is not true. If I use a batch file to run the setup.exe with the TRANSFORM= option to point to the MST it installs just fine from the same share as the managed points to. I cannot see why this is now failing. No permissions change, no shares are missing, nothing has changed. If I switch the admin share back to an SP2 version hey presto it rolls out perfectly as before. If anyone has any ideas please help as I'm at my wits end after months of frustrating dead ends. Thanks Rob
×
×
  • Create New...