Author |
|
k2zs Senior Member
Joined: October 22 2009 Location: United States
Online Status: Offline Posts: 113
|
Posted: December 08 2009 at 07:58 | IP Logged
|
|
|
I have been working with PH2 on my main workstation here and would like to transfer it to a dedicated PC so it is always available, I have different Log In's for this PC for myself and my kids. What files would I have to transfer to the new PC to maintain all my current devices, macro's, triggers, timed events, and web center?
Edited by k2zs - December 08 2009 at 08:00
__________________ Scott, K2ZS
Home Automation Ideas
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: December 08 2009 at 12:16 | IP Logged
|
|
|
Don't know about the web center stuff but the other information is in the PH database. Do a full install of Powerhome on the other system. Then copy powerhome.db and maybe powerhome.ini. The later has various options for startup and shutdown that you may have changed but it may have install specific information as well. I would look at the information in that file on the new system to be sure nothing PC specific would be lost by just copying the .ini file from the old system.
EDIT: macros are in the PH database
Edited by grif091 - December 08 2009 at 18:04
__________________ Lee G
|
Back to Top |
|
|
jpcurcio Senior Member
Joined: April 01 2007 Location: United States
Online Status: Offline Posts: 119
|
Posted: December 08 2009 at 17:03 | IP Logged
|
|
|
Do a clean install on the new machine, and then copy over
the database directory, the plug-in directory, any macros
you may have, and the powerhome.ini file. That should do
it.
|
Back to Top |
|
|
k2zs Senior Member
Joined: October 22 2009 Location: United States
Online Status: Offline Posts: 113
|
Posted: December 08 2009 at 19:04 | IP Logged
|
|
|
OK Thanks Lee, do I do the whole database directory and plugin directory as well?
__________________ Scott, K2ZS
Home Automation Ideas
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: December 08 2009 at 19:38 | IP Logged
|
|
|
I think all you need is the powerhome.db file from the Database subdirectory. I have only a few files in that subdirectory which were generated by the various migration utilities moving from 2.0 to 2.1 to 2.1b and one that is an original large .db file before running the phupg.exe utility to compress the database after doing a trim operation. None of those are needed to run my current PH environment. There is a sample file but that was created during the install and will already be in the new database subdirectory. I would archive your existing powerhome directory/subdirectory structure to a CD/DVD for backup just to be safe.
If you added plugins then those need to be copied or added to the new system. I have not added any plugins so I don’t know if adding a new plugin is just putting a copy into the plugins subdirectory or there is some add process that also sets registry values, .ini values etc. If adding plugins is a process then you should do that process on the new system to be sure all things are setup for the new plugin. Otherwise a simple copy should suffice (assuming plugins other than those that come with PH were installed). Otherwise the base set of plugins that come with a PH install will be in the new subdirectory after the PH install on the new machine.
EDIT: thanks jpcurcio. I did not repeat that in this post but as noted in my first post, the .ini file information, either by coping the file or otherwise needs to be checked against the new install. The new install should have the license information as that is collected during install of the new system but there may well be updates that were made post install of the old system that need to be carried into the new system. Actually I thought the registration number was in the registry but it could be in the .ini file. The registration number can be found by accessing Help/about on the old system.
Edited by grif091 - December 09 2009 at 00:55
__________________ Lee G
|
Back to Top |
|
|
jpcurcio Senior Member
Joined: April 01 2007 Location: United States
Online Status: Offline Posts: 119
|
Posted: December 08 2009 at 23:44 | IP Logged
|
|
|
grif091 wrote:
I think all you need is the powerhome.db file from the Database subdirectory. I have only a few files in that subdirectory which were generated by the various migration utilities moving from 2.0 to 2.1 to 2.1b and one that is an original large .db file before running the phupg.exe utility to compress the database after doing a trim operation. None of those are needed to run my current PH environment. There is a sample file but that was created during the install and will already be in the new database subdirectory. I would archive your existing powerhome directory/subdirectory structure to a CD/DVD for backup just to be safe.
If you added plugins then those need to be copied or added to the new system. I have not added any plugins so I don’t know if adding a new plugin is just putting a copy into the plugins subdirectory or there is some add process that also sets registry values, .ini values etc. If adding plugins is a process then you should do that process on the new system to be sure all things are setup for the new plugin. Otherwise a simple copy should suffice (assuming plugins other than those that come with PH were installed). Otherwise the base set of plugins that come with a PH install will be in the new subdirectory after the PH install on the new machine.
|
|
|
IIRC, the PowerHome licensing info is in the .ini file. That is essential.
|
Back to Top |
|
|
k2zs Senior Member
Joined: October 22 2009 Location: United States
Online Status: Offline Posts: 113
|
Posted: December 09 2009 at 06:56 | IP Logged
|
|
|
Thanks all for your help, I just realized that the other PC has no open com ports open so I will have to put this off until I build another box.
__________________ Scott, K2ZS
Home Automation Ideas
|
Back to Top |
|
|