JaySwift

Hi Guys Has anybody heard back from Microsoft on this yet? I also logged this issue, but nobody really understood what I was on about and nobody could give me an indication whether somebody is actually looking in to it or not. The computer naming issue is seriously holding us back from putting WDS in to production. JS

Tone, Action Pack Media have been stripped of the ability to perform Administrative installations. Action Pack media is the same as Retail/OEM media. It has been something I have been ranting about since the inception of the MS Action Pack. It was the case with Windows XP and Office 2003. I was hoping it would be different with Office 2007 / Vista but it isn't. Please see excerpt of my recent complaint to MAPS-NA@microsoft.com: "I really do not understand the motivation for disabling these features in the Action Pack media. Isn't the whole point of the Action Pack to enable us to setup Labs and test products and technologies before implementing at our clients??" This was their reply: "We apologize for any inconvenience you may be experiencing with Office 2007. At this time, technical support is not included as a benefit to the Microsoft Action Pack Subscription. In order to obtain paid technical support, please contact the following number: 888-677-9444" Go figure.

Hi Guys First of all, Prathapml, if you don't already work for Microsoft as a Product Deployment Specialist, they should hire you. Your clear intructions and to the point advice makes Microsoft's documentation look like a dog's breakfast! Since Win2K our organisation has been deploying software packages via Group Policy (Intellimirror) and this worked very well for Office 2003. (Add the MSI along with an MST file and there you go.) It was my initial understanding that it would be just as simple with Office 2007, but I notice Microsoft has since pulled the documentation they had on this off their website and instead point you in the direction of BDD 2007 (Business Desktop Deployment). I have played around with this, but it appears the only thing you can do is create an additional packaged that gets deployed along with a Vista image. Does anybody have clear instructions on how Group Policy deployment of Office 2007 can be achieved? I tried adding the EnterpriseWW.msi file via Group Policy, but actual deployment fails with an error that it can not find other source files. In addition to setting the installation states and Product Key etc in the Config.xml, do you also have to specify paths in the file so that the MSI can find the other files it needs to install? (FYI, I was able to successfully create an MSP file using OCT and it is saved in the Updates folder.) Any advice on this would be highly appreciated!! Thanks & regards JaySwift