[wpkg-users] Re : Re : Question about multi-domain environment

[Karl]

No please no more microsoft tools

Is this possible with WPKG?

- Message d'origine 
De : Tomasz Chmielewski [EMAIL PROTECTED]
À : Karl [EMAIL PROTECTED]
Cc : wpkg-users@lists.wpkg.org
Envoyé le : Jeudi, 24 Avril 2008, 17h35mn 37s
Objet : Re: Re : [wpkg-users] Question about multi-domain environment

Karl schrieb:
 Hi Tomasz,
 
 To explain myself a bit more in details we offer services to several 
 domains (around 20) so each of them is another 'company'. I can't call 
 it a company but more a mini-company into a big company let's say.
 
 So everything works on Windows so no Linux or other is used. All the 
 clients are WindowsXP users. Later on (around 2009) maybe Vista will 
 come but for now it's only Windows XP Pro.
 
 The goal we want to achieve is that we can stage machines here at our 
 bench with a WPKG environment or elsewhere with a sort of bootable DVD 
 (with a fully equiped WPKG environment if it needs one).
 We'll install the client to have more options and the ease of deploy maybe.
 Now when a computer crashes, the user can't work anymore and a solution 
 must come so I looking for a method to install Windows XP again from 
 scratch for that computer. That's one of the goals.

I think you're trying to reinvent the wheel. If you're a Windows-only 
shop with Windows servers, read about RIS and group policies. And use 
WPKG after the operating system is deployed.

Another, more flexible option is to use Unattended - 
http://unattended.sf.net


 Another is to deploy applications with groups that were grouped by 
 company or managers or ...

Seems like profiles in WPKG.


 Also deploy some software on a computer after an installation of the OS 
 has been done.

RIS / Unattended.



-- 
Tomasz Chmielewski
http://wpkg.org





__
Do You Yahoo!?
En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible 
contre les messages non sollicités 
http://mail.yahoo.fr Yahoo! Mail -
Reporting bugs, all WPKG mailing lists  http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users

Re: [wpkg-users] Re : Re : Question about multi-domain environment

[Rainer Meier]

Hi Karl,

Karl wrote:
 No please no more microsoft tools
 
 Is this possible with WPKG?

Well, I think you can - but you did not exactly specify what you want to 
do. Your question about multi-domain environment does not really apply 
to WPKG as WPKG does not care about domains (except for accessing user 
accounts).

You might also use a centralized software repository (or synchronized 
software repository) and then just assign your profiles to the clients.

Here is a short description how I use it:

I use WPKG on multiple, completely independent, Windows domains as well 
(all served with Samba, but this is irrelevant).

On my master domain I create a share and put it on a server which is 
available to the clients under the name 'software'. So all clients on my 
master domain access WPKG on \\software\RemInst\wpkg\wpkg.js.

All the software is stored at \\server\RemInst\software\...
\\software\RemInst\software is referred as %SOFTWARE% (see WPKG 
variable definition)

To distinguish between hosts on different sites I prefixed them all 
according to the site. At installation you can use winnt.sif to to 
achieve hostname prefixes. Just specivy ComputerName = * and OrgName 
= site1 - so all host will be named like site1-someRandomValue.

Then I created host specifications like site1-.* and assigned profiles 
to them like site1-default.
To make it even easier you might create a profile called something like 
global-profile and then add it to the dependencies of siete1-default 
- so most of the packages (which are globally the same) do not need to 
be added to each profile, just keep them in the global one.


So now here the clue comes...
I use rsync (well, on Windows there might be similar tools - or use 
cygwin) to synchronize WPKG and the software share to remote sites.

On all remote sites the software deployment server is called 'software' 
so the \\software\RemInst\... paths are valid on all the sites. I do not 
need to prepare custom packages for each site. Even if the server name 
would be different you can just define another path for the %SOFTWARE% 
variable.

This setup allows me to update multiple sites with a simple rsync command.

HTH
Rainer
-
Reporting bugs, all WPKG mailing lists  http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users