|
| | | Supreme Being
Group: Advanced Members
Last Login: 1/21/2004 10:48:00 AM
Posts: 154, Visits: 1 |
| | Is there a way to include the Prism Deploy client in a image so that when I roll out WinNT workstations it is already installed? If I change the name of the workstation that is subscribed to a channel will the PC still remain subscribed to the channel but under a different name? Will I need to manually unsubscribe the old computer from that channel as it will occupy two client licenses? |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 9/3/2008 9:40:39 PM
Posts: 654, Visits: 800 |
| | This is quite a common practice and works quite well in an imaging environment. Simply include the Prism Deploy Client (that is actively subscribed to a channel) in the image that you will use for cloning. After imaging a new machine with this image, it will add itself to the channel with the image's computer name. After you rename the computer, it will re-add itself with it's new name. We recommend that you do not delete the image computer name from the channel, as this will cause the Client to stop it's subscription as soon as it first polls using this name. You can view the properties of this image named computer and uncheck the licensed computer box. This will then no longer be able to have Packages distributed to it (while the computer is using this image name), but it will also no longer use a license.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Supreme Being
Group: Advanced Members
Last Login: 1/21/2004 10:48:00 AM
Posts: 154, Visits: 1 |
| | I did as you mentioned above. I created an image and imaged a new PC. The new computer name is added to the channel but I noticed that under properties for that computer the Licensed Computer checkbox is not selected. Is this because when I created the image the old computer had the box deselected in it's properties? Thanks |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 9/3/2008 9:40:39 PM
Posts: 654, Visits: 800 |
| All computer license information is retained on the server. The client does not have any license information, so whether the image is of a licensed or unlicensed computer won't have any effect. After the imaged computer is renamed and has added itself to the channel, it will be an unlicensed computer until the first Task is assigned to it. Computers added via Direct Install will immediately be licensed, computers added via secondary methods (subscription files, client in image, etc.) will be licensed when first assigned a Task.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Junior Member
Group: Forum Members
Last Login: 11/11/2005 12:01:00 PM
Posts: 10, Visits: 1 |
| I tried including the client in an image created using Sysprep. I named the computer "Image", added the client, ran Sysprep, and saved the image file. So, when I reimaged a computer, Sysprep prompts for a Computer Name, which I called Test1. The machine reboots as Test1, and Test1 is then subscribed to the Channel but "Image" is not. So when I imaged another computer and called it Test2, Test2 did not subscribe. Has anyone had success including the Client in an image using Sysprep? I can't figure it out. |
| |
|
|