FrozenLiquidity
[H]ard|Gawd
- Joined
- Aug 28, 2007
- Messages
- 1,588
Quite a title, I know.
Seeing as how my career in IT is relatively young and some of these terms are over my head, I'll break it down to how I understand it, and see if anyone can point me in the right direction. While this current situation doesn't quite fall into the Networking and Security (rather, lack of networking) it might be moved. I figured this was as close as it would get to being in the right place though.
So here's the deal. Our standard deployment is done over a network (PXE, network image, all that jazz) however we're now in a situaton where we need to deploy a small number of clients to a remote location, and are unable to use the network connection there for deployment from PXE. Instead, we've got to revert to an image, but the problem with the image is that things which require unique system identifiers (and agian, feel free to correct me) like SCCM will all have the identifier associated from the image. So when that is taken and deployed to a dozen other computers, suddenly the unique ID's are no longer unique. While I'm not sure exactly what this does within SCCM yet, I think it's safe to say that it should be avoided.
The question is, how can we create an image with SCCM implemented on it for our client workstations, while retaining their uniqueness? Is there some wildcard key that can be used in this case that will prevent conflicts or assign unique ID's in a similar way that a DHCP server assigns IP addresses?
Does anyone know the way to do this? Perhaps a few links to point me in the right direction? I'm having a hard time finding information about how to do this.
Again, I apologize if this isn't as clear as it could be, or is too dumbed-down for some of you real knowledgable types. This just kind of got dumped on me and I am in way over my head. Help me out and throw me a life preserver!
Seeing as how my career in IT is relatively young and some of these terms are over my head, I'll break it down to how I understand it, and see if anyone can point me in the right direction. While this current situation doesn't quite fall into the Networking and Security (rather, lack of networking) it might be moved. I figured this was as close as it would get to being in the right place though.
So here's the deal. Our standard deployment is done over a network (PXE, network image, all that jazz) however we're now in a situaton where we need to deploy a small number of clients to a remote location, and are unable to use the network connection there for deployment from PXE. Instead, we've got to revert to an image, but the problem with the image is that things which require unique system identifiers (and agian, feel free to correct me) like SCCM will all have the identifier associated from the image. So when that is taken and deployed to a dozen other computers, suddenly the unique ID's are no longer unique. While I'm not sure exactly what this does within SCCM yet, I think it's safe to say that it should be avoided.
The question is, how can we create an image with SCCM implemented on it for our client workstations, while retaining their uniqueness? Is there some wildcard key that can be used in this case that will prevent conflicts or assign unique ID's in a similar way that a DHCP server assigns IP addresses?
Does anyone know the way to do this? Perhaps a few links to point me in the right direction? I'm having a hard time finding information about how to do this.
Again, I apologize if this isn't as clear as it could be, or is too dumbed-down for some of you real knowledgable types. This just kind of got dumped on me and I am in way over my head. Help me out and throw me a life preserver!