I get You are not authorized to access this page. when i click on the link you posted.

nelson

--I get You are not authorized to access this page. when i click on the link you posted.

What? That can't be! This site was tested so that there can't be any bugs.

I'll find an admin to pester. Thanks

Hi All,

Some of the content on the Connect site is moderated prior to publishing - that explains why you're currently not able to access the article Cobra7 has submitted. Articles, downloads and videos are the moderated content type. Each section has it's own editor responsible for publishing content. Your article will be published soon, please be patient. In the meantime Cobra7 (and anyone else who posts anything) you can go to the menu under the "me" tab and click "My content" which will list everything you have posted and whether it's been published or not.

Please be gentle with me, I'm up to my eyeballs in aligators!

Thanks!

Cheryl

I understand, thanks for letting me know.

Just to confirm that all articles are moderated and published after the right time to check the content . This way was also in the previous releases and nothing has changed about this approval process.  Usually takes some days, but I am sure that we have good amins that work well. 

Also, thanks to Ohzone to explain "My content" function. I used a lot this feature in the last portal and find it really useful.

I like the post. The one thing I think users needs to take advantage is the use of deployAnywhere for driver management.  This way you do not have to redo your image to add driver support for new NICs or mass storage drivers. Also, your image is small :)

Do a search for DeployAnywhere here in Connect or the site that I check is

http://www.ghostwiki.org/index.php/Idiot%27s_Guide...

Nelo

I agree, DA is a great tool (heck all of GSS is), and I did mention it once, but as I said in the top, I wanted to try to stay brand independent.

I'll toss the link in a GSS follow up I am in the process of thinking about.

Also thanks for the review :)

This article is very detailed and will help some users I am sure. What I am still wondering is why are people still using quasi-Hardware Dependent Images? This image would be likely dated about a week after making it. Perfect example is Adobe Reader. If this is in your base image, a new one came out yesterday for a critical vilnerabilitty, now what? Do you make a new image or perform additional update tasks each time this happens? Patching, service packs, and SATA drivers aside, you should be able to make an XP image that doesn't need updated for years. I don't know that this 'Generic Image' would withstand the test of time. It appears to me the method of using SPDrvScn would only make this hardware independent for images you currently support. New models would require a new image?

Myself what I do is I keep a copy of the Sysprep folder on the network. When we do get a new model I just toss the new drivers in the folder, toss the generic image I made onto a PC, copy the Sysprep folder from the network to the PC, run the sysprep batch, and re-image.

Not counting image time, it takes about 5 minutes to get/extract the new drivers, 1 minute to copy the sysprep folder, and another minute to run the batch file. So under 10 minutes of work to do an update. As far as new software, it can either be added to the image just as easily, or just install it after the image is done.

So how do you make an image that doesn't need updated for years and has very low post-image time requirments?

Keeping it as bare as possible is how I accomplish that. The image size is about 1.4gig. While it only takes about 5 minutes to deploy, it takes another 40 minutes to finish installing the drivers+software. I guess it depends on how important the low post-image time is to the company. Given the amount of time it takes to unbox and setup the machines, an hour works for us.