Install MSI packages and change computers names throught AD

  • Thread starter Thread starter Ricky
  • Start date Start date
R

Ricky

Hi,

I need some help/advice for two issues:

1. Install MSI packages throught Active Directory
2. Change clientes computes names throught Active Directory when they log
into the domain

For the first point i've read some tips in microsoft newsgroups where some
people talk about Advanced Installer Professional 4.7, a Windows Installer
authoring tool which enables developers and system administrators to easily
build reliable MSI packages.

Is this a good tool?... Has someone tested it?... Is there a better
choice?... I hope someone give me an hand/help.

For the second point i've got no ideia how can i make that happen. I mean to
change computers name through a script and when clients logon their
computers name will change from ie: xyZkkkkk to xyWkkkkk


Thanks,
[]
Ricky
 
Ricky,

Changing the computer name is not an easy undertaking - have you considered
using the opportunity to re-image all the computers to make them conform to
the new naming convention?

I often used the NEWSID tool from SYSINTERNALS.COM to change the name of an
individual machine, but you might need to do something else.

How many of these machines have IIS installed - how many have MSDE?

Bob
 
There are 50 machines and none of them have IIS or MSDE. They only have the
basic client software that is:
windows, office, acrobat reader and zip.

What about installing msi packages?

Thanks
[]
Ricky

Bob said:
Ricky,

Changing the computer name is not an easy undertaking - have you
considered using the opportunity to re-image all the computers to make
them conform to the new naming convention?

I often used the NEWSID tool from SYSINTERNALS.COM to change the name of
an individual machine, but you might need to do something else.

How many of these machines have IIS installed - how many have MSDE?

Bob

Ricky said:
Hi,

I need some help/advice for two issues:

1. Install MSI packages throught Active Directory
2. Change clientes computes names throught Active Directory when they log
into the domain

For the first point i've read some tips in microsoft newsgroups where
some people talk about Advanced Installer Professional 4.7, a Windows
Installer authoring tool which enables developers and system
administrators to easily build reliable MSI packages.

Is this a good tool?... Has someone tested it?... Is there a better
choice?... I hope someone give me an hand/help.

For the second point i've got no ideia how can i make that happen. I mean
to change computers name through a script and when clients logon their
computers name will change from ie: xyZkkkkk to xyWkkkkk


Thanks,
[]
Ricky
 
For the first point i've read some tips in microsoft newsgroups where some
people talk about Advanced Installer Professional 4.7, a Windows Installer
authoring tool which enables developers and system administrators to easily
build reliable MSI packages.

Is this a good tool

That's not talk. It's spam. The Advanced Installer
people spam the MSI groups monthly with their latest
update news. (They update it almost exactly monthly.)

You can do everything with an MSI using simple
VBSript, but the system is absurdly complex. The
various programs are built on top of Windows Installer
to simplify the process.
 
Bob said:
Changing the computer name is not an easy undertaking - have you
considered using the opportunity to re-image all the computers to
make them conform to the new naming convention?

I often used the NEWSID tool from SYSINTERNALS.COM to change the
name of an individual machine, but you might need to do something
else.

Changing names in a domain is fairly simple and straightforward.
With nothing more than PSEXEC and a batch script - one can use NETDOM to
rename all the machines they wish.
 
Thanks for the advice. Can you give me an example how to do that?

How to write an MSI program installer with VBScript? Ayush's
link provides the VBS code to create, edit, manipulate an MSI,
but it's a lot of work. That's why there are things like Advanced
Installer. The WindowInstaller.Installer object provides the
means to do virtually anything via script, but it's very
tedious.

Personally, I would never install with an MSI. The whole
thing is a ridiculous mess. My guess is that Microsoft
deliberately created a Rube Goldberg installer in order
to avoid being sued by InstallShield. The result is a system
so badly designed - and so absurdly overproduced - that
InstallShield is almost guaranteed to stay in business. :)

The only advantage that MSI *might* have is that it seems
to be more trusted in Vista than a simple EXE. (Though I
don't know how the details of that actually work out, if, for
instance, you embed VBScripts in your MSI that you want
to run at install time.)

So what it comes down to, if you want to use MSI, is
that you either buy software that does the dirty work for
you, or you figure out the object model and do it all
yourself with script. I'm sorry that I can't offer better
advice. I just don't know much about specific programs.
You might be able to do some comparison shopping
here:
http://www.installsite.org/

If don't have to use MSI then you might look into
something like Inno Setup, which is a free Windows
installer producer that a lot of people like. I haven't
tried it. Apparently it requires learning a simple script.
But it should be a lot easier to learn than MSI.
 
Hi,

I need some help/advice for two issues:

1. Install MSI packages throught Active Directory
2. Change clientes computes names throught Active Directory when they log
into the domain

For the first point i've read some tips in microsoft newsgroups where some
people talk about Advanced Installer Professional 4.7, a Windows Installer
authoring tool which enables developers and system administrators to easily
build reliable MSI packages.

Is this a good tool?... Has someone tested it?... Is there a better
choice?... I hope someone give me an hand/help.

For the second point i've got no ideia how can i make that happen. I mean to
change computers name through a script and when clients logon their
computers name will change from ie: xyZkkkkk to xyWkkkkk

Thanks,
[]
Ricky

We use desktop authority with msi studio both from scriptlogic to
repackage MSI when needed and deploy them to desktops. The MSI tool
has a nice and very useful feature what they call a 'zero-touch
testing'. Its MSI check-before-setup behaves much like a copy>>null by
penetrating on the destination machine and installing in a simulated
mode. It collects info about files and registry keys on that
destination computer that would hamper the deployment of the package.
Very useful... especially with update/upgrade deployments of huge
packages that sometimes install old or new versions of JRE VM, comctl
updates, security fixes tattooing the registry with thousands of keys.
We usually use it to distribute updates on different software to
different department OUs in a single pass.
 
I appreciate the form you try to pass your knowledge. I'll try to get
through based in your tips/help.

[]
Ricky
 
Thanks Dennis. The tool can also build package to uninstall older versions
of the same software I want to install?
ie: replace office xp by office 2003

Thanks
[]
Ricky

Dennis Bareis said:
Hi,

You can also use my free MAKEMSI tool which simplifies the whole process.

Bye,
Dennis

Thanks for the advice. Can you give me an example how to do that?

Ricky
Dennis Bareis [Microsoft MVP] ([email protected])
http://dennisbareis.com/
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://makemsi.dennisbareis.com/
 
Hi,

Thanks Dennis. The tool can also build package to uninstall older versions
of the same software I want to install?
ie: replace office xp by office 2003

You might need to clarify what you are looking for. Distribution via AD is separate issue
from building MSI. Was Office mentioned in this thread?

MAKEMSI builds or updates MSIs, MSIs can do what you want.
MAKEMSI helps in the creation of many common tasks
including VBSCRIPT or DLL based custom actions.
It is relatively simple to use (people without any Windows Installer skills are using it)
but has no inbuilt limitations.



Bye,
Dennis
Dennis Bareis [Microsoft MVP] ([email protected])
http://dennisbareis.com/
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://makemsi.dennisbareis.com/
 
Office wasn't mentioned in this thread but now I remember that a package
could do the uninstall or other way to archive that is a good way to finish
this issue.

Thanks
[]
Ricky

Dennis Bareis said:
Hi,

Thanks Dennis. The tool can also build package to uninstall older versions
of the same software I want to install?
ie: replace office xp by office 2003

You might need to clarify what you are looking for. Distribution via AD is
separate issue
from building MSI. Was Office mentioned in this thread?

MAKEMSI builds or updates MSIs, MSIs can do what you want.
MAKEMSI helps in the creation of many common tasks
including VBSCRIPT or DLL based custom actions.
It is relatively simple to use (people without any Windows Installer
skills are using it)
but has no inbuilt limitations.



Bye,
Dennis
Dennis Bareis [Microsoft MVP] ([email protected])
http://dennisbareis.com/
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://makemsi.dennisbareis.com/
 
Back
Top