|
I'd like to hear people's experience of USMT, specifically Loadstate. Does it really work well out of the box, grabbing all the data that our beloved users like to hide? Does it get all the required settings/customisations of apps too? And the hardlink store - that scares me a little, the idea that you dump all the user's data onto the same harddisk that you are about to format and trust that it survives the format just seems a little too trusting.
|
#
¿
Feb 10, 2011 08:47
|
|
|
|
| # ¿ Apr 30, 2024 23:41 |
|
|
So, you guys trust it then, that's good to know. But, from what I am reading, you need to run with it a few times to make sure that it is scooping the right stuff. So, if you have an organised shop, then it will work well for you. If you have a bit of a mess, where users aren't tied down too much, there's a fair chance of it missing something. So, perhaps not the best tool for the new sheriff in town, but once things are a reasonably well-managed, it will do the job. And it seems that all of you share my same sceptism for Hard Link Migration. Bunch of cyncics that we are.
|
|
#
¿
Feb 10, 2011 17:00
|
|
|
I've got a question about MDT As I understand it, the official process is: 1) add a default image to MDT 2) add appropriate task sequences 3) deploy to a reference machine 4) capture an image of this reference machine 5) create new deployment share using this captured image 6) create new task sequence 7) deploy to new machines I think I must be missing something pretty basic here: why perform 4-6? 4 is a checkbox selection in MDT, so it seems to be the Right Way, but to me it just looks like you are making extra work. What am I missing?
|
|
#
¿
Feb 24, 2011 11:24
|
|
|
peak debt posted:Mostly for saving time during a large scale deployment. quackquackquack posted:I also skip 4-6 (both in MDT and SCCM). Derpes Simplex posted:Ideally you would skip 3-5 and have all your software as packages, Thanks guys. that makes perfect sense. I've been studying enterprise deployment and, for me, the most interesting part is the point at what one method becomes better than another one - which has lots of variables, depending on your exact company. I've learn that if you read the 'Ticket' thread in SH/SHC at the same time as studying the official material, it is hard not to laugh in disbelief at the Utopian scenarios used in the books. They rarely mention crotchey old secretaries or moronic HR policies.
|
|
#
¿
Feb 25, 2011 03:20
|
|
|
That was my thoughts as well. I believe that MS recommends that you have 500+ PCs to make SCCM worth the effort to implement.
|
|
#
¿
Apr 10, 2011 06:11
|
|
|
Stupid newbie question regarding KMS: I understand that you start the KMS service with slmgr.vbs on a suitable server and this handles all the activation of clients with VLKs What I am unclear about is how this service receives it authentication from MS. i.e. what is the process that happens that allows the KMS to issue activation info to its clients? How does the MS-side of things identify and authenticate this service as one that is allowed to activate clients?
|
|
#
¿
Apr 12, 2011 13:46
|
|
|
marketingman posted:
Ah, I get it. So, you have a KMS key (that presumably was supplied on the paperwork when you signed up for Volume Licensing) and you have to manually install that key on the KMS Host using slmgr. That allows MS to activate the KMS host via the net and gives it the authority to activate n number of clients. When you start up a Enterprise version of Win7, it already has the generic KMS Client keys built in and it activates automagically through the srv in DNS With the KMS service, you can only configure the port number it uses - but not much else except add other OS/editions to the list that it supports. Is that all correct?
|
|
#
¿
Apr 12, 2011 15:40
|
|
|
|
| # ¿ Apr 30, 2024 23:41 |
|
|
marketingman posted:bear shark posted:Thanks. I guess I missed the KMS Host Activation part because it is just too drat simple. My mind was expecting either some console snapin with lots of options (a la VAMT) or at the very least a command line only tool with pages and pages of switches and options - most of which are only understood by 3 people in the whole world.
|
|
#
¿
Apr 13, 2011 06:44
|
|
