Re: Newbie and SMS2003
- From: Arkane <Arkane@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 12 Aug 2005 10:38:06 -0700
Hey Greg,
I've managed to package my own MSIs as this works nicely in with another
initiative I'm trying to push through as well.
What I've found with SMS (SMS 2003 SP1 + Win2K3 SP1, 3 AD Forests), is that
when you create a package and deploy the software (advertise). It seems to
use the wrong MSIEXEC command-line.
It seems to advertise the package for installation, rather than install the
package using elevated privs. As a result, when users click on a package, it
tries to install and fails due to lack of admin rights.
Please tell me I can set defaults for the MSIEXEC command-line stuff, or
will I have to do this manually?
What, in your opinion is the best MSIEXEC command-line to use for a package
that has to be installed PER-SYSTEM (not per-user) and must have no or a
minimal interface and be accessible to all users without further
configuration?
(The MSIs I create have been fixed/patched to suit our site, for example,
tweaking File ACLs/Registry ACLs during the build process to allow students
to run applications without error).
I'm familiar with the benefits SMS can bring (or some of them) and am
working my way through the challenge of at least getting one of our
objectives for approving SMS met. (It's a trial server at the moment, we need
hardware/software inventory and silent application management via an agent).
"Greg Ramsey" wrote:
> No -- doesn't need to be .msi -- can be .exe, .cmd, .bat, etc.
>
> MSI packagers for non-MSI -- IMHO that's a preference thing -- I prefer to
> repackage as little as possible. Any time you repackge, you run the risk of
> omitting something that's needed, or adding something extraneous. . . . I
> always repackage as a last resort. If you have a very solid standard build
> process, repackaging can be a lot more successful than if you have multi-OS,
> multi-build processes.
>
> The .sms (and .pdf) package files are nice, but you won't find them for most
> things you want to install. One nice feature of SMS 2003 is that if you're
> deploying a .msi you can do a Right-Click on Package | New | Package From
> Definition , and browse to the .msi, and it will create unattended and
> attended installations. However, I usually tweak the command lines for .msi
> installations too.
>
> The Scenarios and Procedures guide (from MS) is also good. And the SMS
> Administrator's Companion by Steve Kaczmarek (check amazon.com or
> a1books.com) is a nice reference. It has a little bit of all the MS
> documentation in it, and a bit more too.
>
> SMS is a powerful (and complex) product, but the rewards can be great!
>
> Greg
>
> "Arkane" <Arkane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:E15A125C-BB05-4FB7-8FB7-337B1637CCD0@xxxxxxxxxxxxxxxx
> > Steve,
> >
> > Thanks for those links, following reading your reply I happened to stumble
> > across TechNet's VirtualLabs. Have done 2 of their SMS labs and I feel
> > much
> > more confident about how to install a working SMS server now - that's not
> > to
> > say your links weren't helpful but sometimes having to following basic
> > instruction and do something yourself helps more than reading mountains of
> > technical manuals and whitepapers - it's how I learnt about AD to
> > successfully implement that. I got a test-server, did a few 'example
> > do-this'
> > sort of guides and just played with it really.
> > I used the technical stuff when I wasn't familiar with something or wasn't
> > sure how to do something complex.
> >
> > That all said - I'm curious about software deployment with SMS - does the
> > piece of software you want to install HAVE to be an MSI? Is it better if
> > it
> > is an MSI?
> > Would you recommend me looking at MSI packagers for any non-MSI software?
> >
> > I ask because various posts refer to installing software using MSIs which
> > is
> > a good way of doing it but we have lots of software that is not MSI
> > format -
> > how would I install them (as an example - winzip 7)?.
> >
> > Also (thanks to the VirtualLab), I've found out something above SMS
> > package
> > files, these files appear to define how a package is built and how it
> > should
> > be installed, what would I do if software I bought didn't have this? Could
> > I
> > easily build my own or am I getting confused somewhere?
> >
> > Thanking you in advance.
> >
> > "Steve Thompson" wrote:
> >
> >> "Arkane" <Arkane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:0AF246AF-FCA6-468B-8258-C68D6E3F571E@xxxxxxxxxxxxxxxx
> >> > Quick question - I'm going to be performing an implementation of
> >> > SMS2003
> >> on
> >> > our school network. All clients are Windows 2000/XP, all servers are
> >> Windows
> >> > 2000 and DCs are Windows 2003. We don't plan/nor intend to support any
> >> > 'legacy' systems such as Windows 9x/NT.
> >>
> >> Sounds good so far!
> >>
> >> > Does anyone know of any good places to start in terms of documentation,
> >> > hints/tips etc.. with the install of SMS? I'm familiar with how AD
> >> > works
> >> if
> >> > that's any help (which I doubt). I'd rather go through documentation
> >> > and
> >> at
> >> > least have some idea of what I'm getting myself into BEFORE I start,
> >> rather
> >> > than get it installed/setup and then realise I made a huge mistake at
> >> > the
> >> > start or something.
> >>
> >> Here are some links to get you going:
> >> SMS 2003 home page
> >> http://www.microsoft.com/smserver/default.asp
> >>
> >> Scenarios and Procedures for Systems Management Server 2003: Planning and
> >> Deployment
> >> http://www.microsoft.com/downloads/details.aspx?FamilyId=E0644BB4-2336-4254-8A18-9BC180713F7E&displaylang=en
> >>
> >> Systems Management Server 2003 Concepts, Planning, and Deployment Guide
> >> http://www.microsoft.com/downloads/details.aspx?FamilyId=784838B3-34E0-4122-B3E2-17C5B4EEF8F4&displaylang=en
> >>
> >> www.myitforum.com
> >>
> >> Steve
> >>
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: Newbie and SMS2003
- From: Greg Ramsey
- Re: Newbie and SMS2003
- References:
- Re: Newbie and SMS2003
- From: Greg Ramsey
- Re: Newbie and SMS2003
- Prev by Date: Component Status Errors
- Next by Date: RE: Remote Tools Agent won't install
- Previous by thread: Re: Newbie and SMS2003
- Next by thread: Re: Newbie and SMS2003
- Index(es):
Relevant Pages
|
