Re: Question about "Install Flag"

Tech-Archive recommends: Fix windows errors by optimizing your registry



Could you verify whether the re-installed machines get assigned correctly?
If they are not than the push won't start.

On a side note, although I am more than willing to try and help you with a
technical solution for this, the only good solution here is to tell
these admins that if they redeploy a station, they should send you a mail
once they have finished the redeployment stating the name of the machine.
You don't just go running around re-imaging systems without notifying
anyone, it's called procedure. I know I don't need to explain this to you,
but somebody has got
to put it on their plate.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Sasi" <Sasi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF2FA38E-CCAB-4BAC-8F2E-A2CAE4A102E7@xxxxxxxxxxxxxxxx
> logon installation?I don't have any logon script . is it
> nessecary?according
> to SMS documentations the settings I mentioned before are enough to
> trigger
> an advanced client push installation;but it does not work.
> as all of our client machines are 2kpro and xppro,capinst and legacy
> client
> installations are of no concern to me.I want to trigger an advanced client
> installation automaticcaly ,without any scripts.
>
> "Kerwin Medina [MSFT]" wrote:
>
>> How about logon installation then? In your logon script, you can add
>> capinst
>> to it. If the advanced client is already installed, then nothing will
>> happen. If there is no client yet, then a CCR gets submitted and the
>> client
>> is pushed.
>>
>> "Sasi" <Sasi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:5B3DE3E8-4D63-41D4-A7B0-79E7A2169CE1@xxxxxxxxxxxxxxxx
>> > you know;this is my actual problem:
>> >
>> > I have a win2003 domain.I installed SMS2003 and enabled client push
>> > installation and active directory system discovery agent and almost all
>> > machine on my domain recieved the sms client successfully on the first
>> > run.
>> >
>> > there are some administrators in my company that regularly format
>> > client
>> > machines and re-jion them to the active directory,using exactly their
>> > old
>> > names.these administrators are not that professional that I can teach
>> > them
>> > SMS.and because this reformat and reinstallation process happens quite
>> > frequently and non-predictably;I can't track those reinstalled machines
>> > and
>> > install SMS client on them individually either.I can't even ask those
>> > administrators to list refreshed machines;because sometimes they don't
>> > remember them themselves!
>> >
>> > so I want a mechanism to regularly detect newly installed client
>> > machines
>> > and trrigger SMS client Installation on them.these are the actions that
>> > I've
>> > done already;but have not reached what I wanted:
>> >
>> > 1.activated AD_System_Discovery_Agent to run on a daily basis on 12Pm
>> > everyday(to make sure that all clients are up at the discovery time).
>> > 2.activated HEARTBEAT_DISCOVERY to send heatbeats every 4 hours.
>> > 3.activated SQL maintainance task "Clear Install flag" to clear install
>> > flag
>> > of those clients that have not sent heartbeat in the past 3 days.this
>> > task
>> > runs everyday on 12am and according to logs;ends successfully and DOES
>> > resets
>> > the flag.
>> >
>> > with the above-mentioned settings;I expect the clients to be
>> > automatically
>> > installed after atmost 4 days after their OS refresh;but that does not
>> > happen.for example I currently have a machine which has past 14 days
>> > from
>> > its
>> > OS reinstallation;but has not recieved the client yet.its name even has
>> > not
>> > been mentioned in CCM log of SMS server for a CCR request.even when I
>> > manually remove those old records from console;CCR does not trigger.
>> >
>> > with the point that I DO NOT WANT to assign SMS client using Active
>> > directory;and prefer the SMS to discover and install clients itself;I
>> > kindly
>> > ask you to help me resolve this issue.
>> >
>> > thanks
>> > Sasan.
>> >
>> > "Kerwin Medina [MSFT]" wrote:
>> >
>> >> When you delete a system record (which resides in the SYSTEM_DATA
>> >> table),
>> >> you are also removing the corresponding entries for its discovery
>> >> record
>> >> (which resides in the SYSTEM_DISC table).
>> >>
>> >> DDM, when it processes a DDR, it looks at the SYSTEM_DISC table to see
>> >> if
>> >> the client is already installed and if the global push flag is
>> >> enabled.
>> >> If
>> >> so, this causes DDM to generate a CCR which then triggers a client
>> >> install.
>> >>
>> >> So, the answer to your question would be, yes. In the absence of a
>> >> system
>> >> record (and discovery record), DDM will generate a CCR for an incoming
>> >> DDR
>> >> (assusming that global push is enabled), which should then cause the
>> >> client
>> >> to be installed.
>> >>
>> >> Note however that when you remove a system record, the inventory that
>> >> is
>> >> associated with that record gets lost. Why don't you just do a
>> >> targetted
>> >> push to those machines that you want to install the client to?
>> >>
>> >> "Sasi" <Sasi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:035A2F1C-0F9E-437E-A3F7-897E46278822@xxxxxxxxxxxxxxxx
>> >> > Does deleting the discovered client from the SMS database (using SMS
>> >> > console)
>> >> > resets the install flag of that client?
>> >> >
>> >> > I want to know whether just removing a client from the console ,is
>> >> > enough
>> >> > for Client Push Installation to trigger installation on
>> >> > re-discovered
>> >> > client;or I have to run "clear install flag" maintanance task in
>> >> > addition
>> >> > to
>> >> > deleting and re-discovering the client.
>> >> >
>> >> > I want to make sure that a client that is previously discovered and
>> >> > installed ;gets SMS client installed automatically,if it is
>> >> > reformated
>> >> > and
>> >> > has the OS reinstalled and re-joined to the active directory using
>> >> > its
>> >> > old
>> >> > name.
>> >>
>> >>
>> >>
>>
>>
>>


.



Relevant Pages

  • Re: SMS 2k3 Advanced Client not installing...
    ... Can you run a command session as local sytem and try to do a net stop on the ... > may try on one client to remove BITS then re-install the advanced client. ... >>> Have you configured your Push Installation account? ... I can't tell you SP level on>> all machines, is there a minimum I might be missing? ...
    (microsoft.public.sms.setup)
  • Re: XP clients do not appear in Collections
    ... So your XP machines are or are not being discovered? ... installation methods have NOT been enabled. ... Very soon after enabling the discovery methods, ... >>> have any site listed or indicate the client has installed. ...
    (microsoft.public.sms.admin)
  • Re: SMS 2k3 Advanced Client not installing...
    ... may try on one client to remove BITS then re-install the advanced client. ... It appears that either the BITS installation is failing or>> you are getting permission denied. ... I can't tell you SP level on> all machines, is there a minimum I might be missing? ...
    (microsoft.public.sms.setup)
  • Re: Adv Client - Causing MSI Installation Issues
    ... machines to go through and we have had to slow down the role out immensely ... SMS client was pushed on the machines using client push installation ... >> Event Source: MsiInstaller ...
    (microsoft.public.sms.setup)
  • Re: SMS Virtual Mouse Problem
    ... Desktop Client on the machines but what we could not understand is that why ... About the Problem of the lose of drivers after the installation of SMS. ...
    (microsoft.public.sms.admin)