Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Image not replicating but says its fine on Site server

Created: 25 Apr 2013 • Updated: 06 May 2013 | 8 comments
This issue has been solved. See solution.

I got a problem with an image file not replicating. on the site server it says file downloaded and ready but when I checked the file size it was only half the size.  I deleed teh image file and guid folder and tried updating but packages but it dint update. It now says package is ready and downloaded even though there is no folder on the site server. any one got any ideas!

It also says the package size is 0KB

p.s. The location of the image on the NS is greyed out - I dont know if thats meant to be. Any images inported into NS and residing on it are not (dont know if this is related.)

How can I refresh this

 

Operating Systems:

Comments 8 CommentsJump to latest comment

Thomas Baird's picture

There is more than just a greyed out image involved here.  First, if it's greyed out, I'm guessing it says there's an invalid location.  In fact, it sounds like the package was captured on a Site Server, and that original location / site server is no longer available.  Look at the location there and see if it's actually - in existence, and map to it from the SMP / NS Server to verify the NS can see it.

 

Other thoughts:

Is it the only image you have?  Any others working?  Do you have the original image file somewhere?  If so, you might try to import it with the Resource import tool: \\server\deployment\task handler\tools.  It will create a new resource with preferrably a new name (be sure to name it well) and that might then work.

Thomas Baird
Technical Solutions Architect @ www.xcendgroup.com
https://www2.gotomeeting.co

BugTastic's picture

Hi Thomas, hanks for the reply. when I checked the image settings, under 'Package Servers' tab - the 'Package Destination Location on Package Servers:' Was not ticked. I ticked this and put int he location it should be ( \\%COMPUTERNAME%\\deployment\task handler\image\<GuiID>) this done the trick. No idea how that happened. The image location is still greyed out, and yes, it was created on a site server as out NS is in a datacentere. thats no big deal though as it works.

Thanks

 

SOLUTION
md investigate's picture

Hi,

it's greyed out because the image was not captured or imported on NS. Have a look on following for  background information http://www.symantec.com/docs/HOWTO21731

In 7.1 you are able to capture an image on every siteserver but for correct functionality it is needed to be imported into NS. There is a tool for this, mentioned in the linked article.

 

Regards

BugTastic's picture

Hi, thanks md. When you say correct functionality, what do you mean. I dont see any benefit of copying a large image file to a NS server that sits in a datacentre and will not be used to deploy an image. What benefits would I see copying/importing this into NS ?

Thanks

Thomas Baird's picture

Technically none.  You are correct.  MOST customers don't capture/distribute that way, and having the image on a site server puts it at risk only because if the Site Server is removed and the image deleted from it, even if it has replicated, all copies will be lost because the "source location" is gone.

But you are correct - if it was capture there, to be used only there, there's no reason to "bring it back home" to the NS.

Thomas Baird
Technical Solutions Architect @ www.xcendgroup.com
https://www2.gotomeeting.co

md investigate's picture

Hi,

I wrote it misunderstanding. You have all functionality but any client served by the ns directly as task/package-server couldn't get the image. But as far as I understand your NS serves no client, right?  

So you are safe to rollout.

One more thing to mention: I always view on my site servers as always be replaceable. So if there is any defect on one I only have to take new hardware / vm , install site server agents etc and let the automatism work itself. But for this you need all resources on a central stable place (the NS is defined to be this stable place). In the article mentioned in point 5 this is described as well. Sure, it's something about strategy but when I have to replace a Site Server I don't want to mind about "was there an image captured by him? Is it safe to replace it?" etc...

 

Regards

BugTastic's picture

Thats a good point about replacing the site server if the image is on that one. Something to think about there. Grrrr :-)

Thanks

 

Thomas Baird's picture

We have asked for a way to "fix" this ... oversight ... in the future, but unfortunately will NOT get it in the next release.  I'm still pushing for something "like" what the software library is.  We'll see.

Thomas Baird
Technical Solutions Architect @ www.xcendgroup.com
https://www2.gotomeeting.co