Highlighted
Absent Member.
Absent Member.
1838 views

Filr Deployment

Hey Guys,

Trying to deploy the Filr client over here.

Using the MSI, I find that during the install the explorer shell is killed and re-loaded during the install.

Windows 7 see this as unexpected, and asks if you want to re-launch explorer.

If you do this, the install tries to load explorer again and kinda keeps explorer from loading properly.

If you close out of the "restart explorer.exe" prompt, the Filr install continues on just fine.

I'm running the install as a Dynamic Administrator, and this happens on Windows 7 and Windows 8 clients.

It looks like a full re-load of the user profile (e.g. user profile settings being created box shows up in the upper left of the primary monitor).

Anyone else experience this?

Jacob
Labels (2)
0 Likes
10 Replies
Highlighted
Visitor.

Re: Filr Deployment

We saw a phenomenon where explorer crashes and is restarted during Filr client install. Both on XP and W7. This was reported. I am not sure what the status is. I'll try to find out.

-- Bob
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

Bob et. al.,

I've received confirmation from Novell - this was a change in the 1.0 release of Filr - instead of requiring a reboot, they're killing and restarting explorer.exe.

I've also confirmed that XP sees this as a crash, with an even scarier message including memory addresses and such.

Trying to work around this with some script-fu.

pitcherj
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

pitcherj wrote:

>
> Bob et. al.,
>
> I've received confirmation from Novell - this was a change in the 1.0
> release of Filr - instead of requiring a reboot, they're killing and
> restarting explorer.exe.
>
> I've also confirmed that XP sees this as a crash, with an even scarier
> message including memory addresses and such.
>
> Trying to work around this with some script-fu.
>
> pitcherj


Thanks for the heads up. Sounds a bit drastic to kill the explorer.exe
- maybe that's just me, I could live with a reboot being required.

--
Niels

A true red devil...

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

nop1983;2264762 wrote:


Thanks for the heads up. Sounds a bit drastic to kill the explorer.exe
- maybe that's just me, I could live with a reboot being required.

--
Niels

A true red devil...


nop1983,

I agree...

Would be nice if the installer prompted for a reboot using the normal MSI facilities, and if I set the REBOOT=REALLYSUPPRESS flag, just ignore it and move on with life, or allow me to prompt a reboot with ZENworks...

pitcherj
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

pitcherj;2264727 wrote:
Bob et. al.,

I've received confirmation from Novell - this was a change in the 1.0 release of Filr - instead of requiring a reboot, they're killing and restarting explorer.exe.

I've also confirmed that XP sees this as a crash, with an even scarier message including memory addresses and such.

Trying to work around this with some script-fu.

pitcherj


I tried a couple different ideas without being able to work around explorer.exe being killed (including killing it myself with an end process action in ZCM before running the installer).

Looks like a fix/workaround/resolution is going to have to come from Novell...

pitcherj
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Filr Deployment

There is a Registry key that will cause explorer.exe to restart.
perhaps tweaking that, killing explorer.exe, and then installing, fixing
key and starting explorer.exe may help.

again, a work around at best if you want to use best anywhere near that
idea 🙂

On 5/22/2013 2:26 PM, pitcherj wrote:
>
> pitcherj;2264727 Wrote:
>> Bob et. al.,
>>
>> I've received confirmation from Novell - this was a change in the 1.0
>> release of Filr - instead of requiring a reboot, they're killing and
>> restarting explorer.exe.
>>
>> I've also confirmed that XP sees this as a crash, with an even scarier
>> message including memory addresses and such.
>>
>> Trying to work around this with some script-fu.
>>
>> pitcherj

>
> I tried a couple different ideas without being able to work around
> explorer.exe being killed (including killing it myself with an end
> process action in ZCM before running the installer).
>
> Looks like a fix/workaround/resolution is going to have to come from
> Novell...
>
> pitcherj
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

craig_wilson;2264780 wrote:
There is a Registry key that will cause explorer.exe to restart.
perhaps tweaking that, killing explorer.exe, and then installing, fixing
key and starting explorer.exe may help.

again, a work around at best if you want to use best anywhere near that
idea 🙂

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


Craig,

Mind sharing what that registry entry is that you're speaking of?

Jacob
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Filr Deployment


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\AutoRestartShell


On 6/4/2013 9:16 AM, pitcherj wrote:
>
> craig_wilson;2264780 Wrote:
>> There is a Registry key that will cause explorer.exe to restart.
>> perhaps tweaking that, killing explorer.exe, and then installing,
>> fixing
>> key and starting explorer.exe may help.
>>
>> again, a work around at best if you want to use best anywhere near
>> that
>> idea 🙂
>>
>> --
>> Craig Wilson - MCNE, MCSE, CCNA
>> Novell Knowledge Partner
>>
>> Novell does not officially monitor these forums.
>>
>> Suggestions/Opinions/Statements made by me are solely my own.
>> These thoughts may not be shared by either Novell or any rational
>> human.

>
> Craig,
>
> Mind sharing what that registry entry is that you're speaking of?
>
> Jacob
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

In windows xp the shell is being restarted as local admin in our environment. This is installing from a user account with Dynamic Admin rights. This means that we cant let staff run this bundle since they would then have access to install/modify anything they wanted until a reboot.

Hand installs by our tech staff only seems to be the best option unfortunately. I made a bundle to copy the files down and launch the installer to make life a little easier for them.
Would love for the end users to be able to set this up on their own though without getting admin rights.

craig_wilson;2264780 wrote:
There is a Registry key that will cause explorer.exe to restart.
perhaps tweaking that, killing explorer.exe, and then installing, fixing
key and starting explorer.exe may help.

again, a work around at best if you want to use best anywhere near that
idea 🙂

On 5/22/2013 2:26 PM, pitcherj wrote:
>
> pitcherj;2264727 Wrote:
>> Bob et. al.,
>>
>> I've received confirmation from Novell - this was a change in the 1.0
>> release of Filr - instead of requiring a reboot, they're killing and
>> restarting explorer.exe.
>>
>> I've also confirmed that XP sees this as a crash, with an even scarier
>> message including memory addresses and such.
>>
>> Trying to work around this with some script-fu.
>>
>> pitcherj

>
> I tried a couple different ideas without being able to work around
> explorer.exe being killed (including killing it myself with an end
> process action in ZCM before running the installer).
>
> Looks like a fix/workaround/resolution is going to have to come from
> Novell...
>
> pitcherj
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Filr Deployment

pitcherj wrote:

>
> nop1983;2264762 Wrote:
> >
> >
> > Thanks for the heads up. Sounds a bit drastic to kill the
> > explorer.exe - maybe that's just me, I could live with a reboot
> > being required.
> >
> > --
> > Niels
> >
> > A true red devil...

>
> nop1983,
>
> I agree...
>
> Would be nice if the installer prompted for a reboot using the normal
> MSI facilities, and if I set the REBOOT=REALLYSUPPRESS flag, just
> ignore it and move on with life, or allow me to prompt a reboot with
> ZENworks...
>
> pitcherj


Yes, that would have been a better way to go by this. Not sure if they
planned to change this, did they mention anything about that in you SR?

--
Niels

A true red devil...

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.