Re: SMS questions/concerns
From: TerryM (nospam_at_hotmail.com)
Date: 08/05/04
- Previous message: Curt Shaffer: "Re: SMS questions/concerns"
- In reply to: Curt Shaffer: "Re: SMS questions/concerns"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Aug 2004 18:58:42 -0700
SMS Installer newsgroup is funny.
It is actually a tool that can be downloaded from the SMS site and can
create repackaged applications that SMS can use. It also requires a SMS
license to use it. However the repackaged applications it creates can be
used by any software distribution method not just SMS and you can even
create little utilities using it, kind of like a light version of vb. It
has no real requirements on SMS.
But I think many people think it is a newsgroup about installation issues
since they see the "installer" part.
It's not that big of a deal, I usually just tell people so they can get more
answers from a wider audience looking to specifically answer SMS related
questions by posting on a SMS specific newsgroup.
Good luck,
Terry
"Curt Shaffer" <curt@chilitech.net> wrote in message
news:ces0qq01pl2@enews2.newsguy.com...
> Thanks for the info.
>
> I appreciate your input a lot. That is the kind of input I wanted. Just to
> be clear I thought Microsoft.public.sms.installer was an SMS newsgroup.
But
> you did bring up a lot of considerations and I will take all of that into
> account. I did not even think about needing admin rights on their boxes.
And
> about the suing thing, I thought of that and figured on a TOS of some sort
> that would say that all patches would be thoroughly on our systems, but
that
> sometimes given the way things are, they do odd things. As well as making
> sure that sometimes viruses and such still get in and we would not hold
100%
> liability of that, but we would offer assistance in the case that
something
> like that would occur. Anyway I will end on that note. Thanks again for
your
> help Terry ; )
>
> Curt
> "TerryM" <nospam@hotmail.com> wrote in message
> news:%23ds0MTneEHA.636@TK2MSFTNGP12.phx.gbl...
> > Well first off, I would say you should post this to a SMS newsgroup to
get
> > more helpful suggestions.
> >
> > Also I would say this sounds like a big headache for your particular
> > situation. Using SMS 2003 and SP1 would probably help a little bit but
> > the
> > problem is you need to have a single account that has admin rights to
all
> > the machines you would be managing. Also if you wanted to do remote
tools
> > you could just use the stuff included with windows like remote
assistance
> > and remote desktop and even netmeeting or VNC... As for the Software and
> > hardware reports not sure what you would do with these? it just sounds
> > like
> > a lot of network traffic to be adding to your environment for little
> > benefit?
> >
> > The patch management piece would be nice, but again as a company you
might
> > be opening yourself up to things. What happens if you push a patch to
> > someone and it breaks their machine? Could they sue you? What if they
> > think it broke their machine but it didn't? You'll have to spend a lot
of
> > time proving it didn't. Companies can do these things because they own
> > the
> > machines but from the way your post sounds, these are just customers of
> > yours.
> >
> > You could set policies that these machines need to be patched or running
> > at
> > a certain level but it is hard to enforce. You could set something that
> > if
> > a particular machines keeps bringing down sections then after X amount
of
> > times they no longer can have service with you or something though??
> >
> > Anyway that's just my 2 cents... like I said if you post to a SMS
> > newsgroup
> > others may have more ideas for you.
> >
> > Terry
> >
> > "Curt Shaffer" <curt@chilitech.net> wrote in message
> > news:ceqtg70b8q@enews2.newsguy.com...
> >> We are and ISP and offer high speed wireless internet locally. We we
> > tossing
> >> around the idea of offering SMS to our customers as an opt-in service.
> > There
> >> are a few questions and concerns that we have that I was hoping to get
> >> answers for. Here they are:
> >>
> >> 1. We will not really know what kinds of software,hardware, etc that
> >> everyone will have. So with that in mind, have there been any issues
with
> >> the clients not working with certain setups(software or hardware) out
> > there
> >> that anyone has experienced?
> >>
> >> 2. Our network is a bridged network, and most of our customers use
> > routers,
> >> so with that in mind; We will have to open ports for the different
> > services.
> >> We block a lot of the ports on our edge routers so we are not worried
> >> with
> >> that, but we are worried about other people on the network poking
around.
> > So
> >> does anyone out there have this kind of setup, and if so how do you
> >> handle
> >> it. If not are there any suggestions?
> >>
> >> 3. Are there any caveats with SMS that I am missing that would make
this
> >> idea a bad one?
> >>
> >> The main reason we want to do this is that our wireless network gets
> >> hammered,potentially effecting all of a sector, because of customers
not
> >> keeping up to date with windows and AV programs. But we would also like
> >> to
> >> use some of the other features like offering free software and
> >> troubleshooting with RDP and the hardware/software reports that are
> > already
> >> in SMS.
> >>
> >> Thanks for all of your help
> >>
> >> Curt
> >>
> >>
> >>
> >
> >
>
>
- Previous message: Curt Shaffer: "Re: SMS questions/concerns"
- In reply to: Curt Shaffer: "Re: SMS questions/concerns"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
