Jump to content

thieske

Member
  • Posts

    38
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Ukraine

About thieske

thieske's Achievements

0

Reputation

  1. Pfff. NERO Winamp Winrar Winace Winzip K-lite k++ (no spam, no addware) Sygate PF Installshield adminstudio 5.5 Ad aware (need a good substitute) Google bar (need a good substitute) MSN Some games Enemy Territory UT2004 Age of Mythology Game extra's Etmin Pathfinder Teamspeak
  2. one short question... If and when there is already an installation of f.i. Office 2000 on the machine... Is it possible to automaticaly uninstall it, or do i have to write a script which executes the uninstall sequence...
  3. Helleuw all, I've been quite busy lately, i need to show u ppl this in order to be sure that i described the following process right... I'm installing XP office pro on workstations with the help of policy's in the Active directory 2003 (assigned to install on logon...) When the pro.msi is called upon by the workstation does automatically look if there's a transform file in the same directory as where the pro.msi is? Well here's my mini-mini-guide so far... 1. make an admin-installation of XP office (which includes the reg-key) e:\setuppro /a; 2. Share the directory in which u've installed Office XP; 3. Create a mapping to the share, locally on the server; 4. Create a policy in which u assign office XP to usergroups (policy is created in an OU= Organisational Unit), U should assign the pro.msi from the mapping u've created; 5. Use ORK (office recource kit) to create an transform file (is it needed?); 6. Start the client, and log on with a username which is in the specified usergroup where the policy applies to. badabing, u've got a client with XP office pro installed !!!
  4. Well, i've created the MST-file with the "ORK" program, is it only possible to start it with setup.exe or can i simply execute pro.msi to install OfficeXP with the included registry code EDIT: should have read better
  5. two questions stated in my topic start... Is it hard to create a MST-file ??? I want to deploy office XP with policy's (using pro.MSI and the cabinet) Is it possible to create a file which tells the MSI to include a serial number??? my guess is it's possible only the answer isn't to convenient, had found some info on this board on this, but it wasn't specefic enough to help me on my way...
  6. is it possible? I want to deploy office by using policy's in the active directory 2003. Works super, i can assign the install etc. What i want now is that it is installed, and when i start f.i. "word" it won't prompt me the reg-key....
  7. AD stands for active directory, i assume that u know what ppl can do with the AD? U can deploy office by using it's MSI files, u can set a deployment policy in the active directory to organisational units (OU), add your computer to a certain OU after u logged it onto the AD, and then log on again, the assigned MSI files will be installed automatically... but that's after the unattended installation Anyway i further don't know if there's any network connection after the initial copy process, if so someone else here in this board should provide u that answer...
  8. here's the hard part, i believe that's impossible, because after the 1st reboot there's no connection with the server anymore, scince XP copied all files locally to your harddrive my guess is that u should do the same with office etc. with the /RX: specification that should be possible, the files will be copied to your hardrive in a matter of a few minutes and will be available for install while the XP installation isn't done... after the installation the files will be deleted... otherwise u could distribute the software with the AD, if u set the software to be assigned, the computer will recieve all assigned software on the 1st logon on the network...
  9. well, it's practically the same, i just use them without the variables... it's because i execute them without a batch file, and when my research is done i will add the line to a batch with some comments etc.
  10. what happens is this, when u start the winnt.exe u should type this... winnt.exe /u:<mapping>:\<answerfile> /s:<mapping>:\<i386map>mine looks like k:\i386\winnt.exe /u:k:\i386\winnt.sif /s:k:\i386If u start your unattended installation like that then install copy's all needed files to ure Harddrive and from the moment of execution and the "taking out floppy" the rest will be done magically unattended Ai: i dig ure problem, u can specify a folder which will be copied to your local drive, and then all z:''s should be replaced by local paths... from the below your winnt.exe execution might look like this k:\i386\winnt.exe /u:k:\i386\winnt.sif /s:k:\i386 /rx:k:\i386\$oem$ Should be in here
  11. yourtech, i hope u left the bootdisk that could be downloaded from the link origininal, there's no need to add emm386.exe to it, cuz it has it's own mem managers... Just to be sure
  12. just execute smartdrv.exe twice the second time it shows u what it has done to your disc i placed smartdrv on the share, and execute it from there, is somewhat faster then a floppy method i also use mem.exe for debugging the config.sys if nessesary
  13. for your info... Did u start smartdrive, otherwise the "hang" could take a long while i did it without smartdrive took the computer 3 hours to begin the next session to copy, it looked like the system hanged itself up but that wasn't so... Be patient, and use SMARTDRIVE, really i mean it EDIT: the installation is failed when u get a nice divide by 0 error or something like that... BTW keep ure hands of the machine and make sure that after u started the installatation to get the floppy disk out of the drive... i don't know on what kind of machine you are working on, i'm testing on a PII 350 Mhz 128 MB ram and a 10Mbit networkcard (it takes about 1,5 hour to install)
  14. Euhm, i was a little bit impatient there, actually i don't have any problems with rebooting, the unattended install works like a dream right now, i'm finally blessed with a working method!!!


×
×
  • Create New...