|
| | | Forum Newbie
Group: Forum Members
Last Login: 9/25/2007 6:48:03 PM
Posts: 3, Visits: 5 |
| | Hi at New Boundary. Been using Prism Deploy for about 4 months now. So far we have manually (direct push) installed the client whenever our machines needed re-imaging. I know that you can install the client .exe through a computer startup script using IF statements, and it seems to work fine. What I'm wondering is what happens if I roll out a windows XP image onto machine X. The logon script installs the client and I deploy some packages. A few days later I want to re-image the computer and upon boot, the client will be rolled out again, onto a computer with the exact same name, in the exact same OU. What happens now? Will Prism Deploy automatically remove the former client from the console and re-establish connection to the new client or will there be some sort of conflict in the console? Thanks in advance, SJO |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| In this case you would have two computers in the Console with the same name. One of them (the "new" one) would be actively polling, the other one would be inactive. The last poll time on the "old" computer will no longer be updated. In the database, these two objects have different names. You should delete the inactive computer to free up its license.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|