Hi Everybody,
Now that Windows 10 Migration is coming slowly but surely.Can someone help me understand How different is it from windows 7 from a packagers perspective.
To be specific, how different will it be for a Packager on windows 10.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
Ask yourself this first: under the hood, what's *really* different about Windows 10 versus Windows 7, in terms of the apps which would require a packager? I'm holding up the fingers of one hand. I'm not expecting to need another hand...
Answered 08/22/2016 by: VBScab
Red Belt

  • I'm packaging for Windows 10 at the moment (app-v and windows installer). I agree with VBScab's comments, so far I see minimal changes that would affect* packaging.

    *Is that correct affect/effect. //Shrugs.
    • "Affect".
    • Thank you rileyz....though there is no predominant change....but as you mentioned (minute change)can you mention some of those minimal changes...please.
  • I'm holding up the fingers of one hand......i;m not expecting to need another hand...can you expalin that please...bit of a ridle for me.
Please log in to comment

Answers

0
Never heard the expression "I can count on the fingers of one hand the number of times that [insert event of your choice] has happened"?
Answered 08/22/2016 by: VBScab
Red Belt

Please log in to comment
0
in terms of differences they are minimal, however its when you get into other things that differences/issues start to pop in, such as if you're currently using app-v 4.6 i'm afraid you will need to dump it as its not supported in windows 10 and we have identified issues where entries in the VFS are not populating on occasion and requiring a complete removal and re-instatement of the package on the windows 10 machine so that will need a move to 5.1 (this is now a component to be enabled in the OS now)

our biggest problem by far is Appsense in windows 10, some of our EM's are temperamental at applying and UP doesnt work at all (after speaking with Appsense apparently it was a change done in windows 10 that basically broke UP in Appsense with windows 10)

so currently we are now migrating across from app-sense EM to Microsoft AGMP and from Appsense UP to UE-V 2.1 SP1 as this still works and offers a better capture process than running UP (especially with our app-v packages)
Answered 08/24/2016 by: sparky86
Fourth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity