Clean System
Apologies for the Newbie question, I have googled and couldn't find a definitive answer.
With regards to creating a "clean system" for repackaging applications. Ideally, would I want to have that system joined to the domain where the application would be deployed on? Or would clean system be best to be off the domain to maximize its "cleanliness".
Also, if anyone has experience repackaging accounting applications I'd love to hear from you. I am network admin for an accounting firm and need to repackage such archane applications as Quickbooks, PROfile, CaseWare, and WinTOD. In my limited attempts I've only managed to get WinTOD to work, so any advice on the others would be appreciated.
With regards to creating a "clean system" for repackaging applications. Ideally, would I want to have that system joined to the domain where the application would be deployed on? Or would clean system be best to be off the domain to maximize its "cleanliness".
Also, if anyone has experience repackaging accounting applications I'd love to hear from you. I am network admin for an accounting firm and need to repackage such archane applications as Quickbooks, PROfile, CaseWare, and WinTOD. In my limited attempts I've only managed to get WinTOD to work, so any advice on the others would be appreciated.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
Bartesque
18 years ago
Sure.
The whole idea doing installation captures on a clean machine is finding the lowest common denominator, you don't wanna do a snapshot of an installation that you already have installed on your system.
Taking a snapshot of your standard system - SOE (Standard Operating Environment - which is not available in Wise standard ed.) you can catch whatever conflict you may encounter when suiting your snapshot to your system, importing it into Software Manager
You'll find it in "Initial Workbench Setup" or in your Tools tab.
Please read Wise Reference Manual for getting familar with Wise, try package some easy apps like WinZip, whatever app you use reaguarly til you get the hang of it and your abilities to customize your installation
The whole idea doing installation captures on a clean machine is finding the lowest common denominator, you don't wanna do a snapshot of an installation that you already have installed on your system.
Taking a snapshot of your standard system - SOE (Standard Operating Environment - which is not available in Wise standard ed.) you can catch whatever conflict you may encounter when suiting your snapshot to your system, importing it into Software Manager
You'll find it in "Initial Workbench Setup" or in your Tools tab.
Please read Wise Reference Manual for getting familar with Wise, try package some easy apps like WinZip, whatever app you use reaguarly til you get the hang of it and your abilities to customize your installation
Posted by:
Bartesque
18 years ago
For a clean snapshot machine you would definatelig not want it on your domain, let alone various GPs being set
The clean snapshot pc i made at work was a clean install of winXP Sp2, installing wise and various tools and the hotfixes being set on the domain. Thats it.
Sometimes you'll need other software to be installed to comeplete your snapshot, .Net Framework, office whatever ...
The trick here is, i think is doing a SOE snapshot on a standard domain machine with stanadrd applications and importing the SOE into your software manager, and it will tell you imidiatly when somethings conflicting
The clean snapshot pc i made at work was a clean install of winXP Sp2, installing wise and various tools and the hotfixes being set on the domain. Thats it.
Sometimes you'll need other software to be installed to comeplete your snapshot, .Net Framework, office whatever ...
The trick here is, i think is doing a SOE snapshot on a standard domain machine with stanadrd applications and importing the SOE into your software manager, and it will tell you imidiatly when somethings conflicting
Posted by:
xxLucidxx
18 years ago
Thanks for the reply. So it sounds like all I need on the clean machine is WinXP+Patches+Wise.
Forgive my ignorance once again, can you elaborate a little more on what SOE stands for and what you mean by "The trick here is, i think is doing a SOE snapshot on a standard domain machine with stanadrd applications and importing the SOE into your software manager, and it will tell you imidiatly when somethings conflicting".
Thanks again for any help.
Also, is there a really good step by step tutorial on how to repackage with Wise for Newbies. I've found a few, but I'm not experienced enough to determine if there are really accurate until I try them and succeed or fail. If anyone knows of any that are tried and tested, please point me in that direction.
Forgive my ignorance once again, can you elaborate a little more on what SOE stands for and what you mean by "The trick here is, i think is doing a SOE snapshot on a standard domain machine with stanadrd applications and importing the SOE into your software manager, and it will tell you imidiatly when somethings conflicting".
Thanks again for any help.
Also, is there a really good step by step tutorial on how to repackage with Wise for Newbies. I've found a few, but I'm not experienced enough to determine if there are really accurate until I try them and succeed or fail. If anyone knows of any that are tried and tested, please point me in that direction.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.