With the release of Ghost Solution Suite 3.0, we are holding regular "How-to" webcasts to help users get up to speed on this new solution as quickly as possible.
Before you attend any of the "How-to" webcasts, please be sure to download and begin testing GSS 3.0 and you may also want to watch some of our GSS 3.0 How-to Videos.
Here's the webcast schedule:
I will update this post with links to register and the topics we will cover as we get a little closer to each date.
Stay tuned!
Why does the link to Ghost Solution Suite 3.2 webinar require additional contact details if I am already logged on Sym account ?
I gave up.
Please join us for our Launch Webcast for Ghost Solution 3.1 on Wednesday, April 20!
Sign-up here!
https://www-secure.symantec.com/connect/events/webcast-ghost-solution-suite-31
Interesting
I found that I needed to set a File Transfer Port, rather than using a dynamic port.
Page 79 of the Symantec™ Ghost Solution Suite 3.0 User Guide.
" Client/server file transfer port: _____. Specifies a static TCP port for file transfers to the clients. The default value is 0 and causes the server to use a dynamic port. This setting is useful if you have a firewall and need to use a specific port rather than a dynamically assigned port. "
Copy and Execute Files?
I have tried to push or copy a file from the sereve to the client.
I have enable File and Print Sharing on the Client.
I get code 10060.
Do I need to open more ports other than 402?
File is placed in the root of the share.
C:\Program Files (x86)\Altiris\eXpress\Deployment Server
The boot menu timeout can be changed without affecting the functionality of automation folders. You can set it to zero if you don't want it to display at all. We set ours to one second so that it barely flickers by (no one really notices it) but if our techs want to purposefully jam the down arrow at the right time they can boot to automation manually. The fact that it is set to 30 seconds is a byproduct of the windows default timeout getting applied after sysprep. The command is:
bcdedit /timeout 1
All you need to do is add that to a run script job that runs in production after imaging. The client will display the menu for 30 seconds the first time after image deployment before booting to production (and potentially during the reboots while setup is installing drivers, etc), but after the script runs it will behave the way you set it.
@David Evans
I'm the Symantec point-of-contact for our school District (+ 3 sister colleges). We've been a “paid maintenance” user of GSS starting with 2.0 and have been following/testing GSS 3.0 since the “Beta” stage. We currently have an "open" ticket with support on this matter which has been escalated.
I concur with AC and have been awaiting the promised "virtual partition" from 2.5.1 which was seamless during deployment and didn't permanenly alter the client. Having followed/tested 3.0 since "beta", both the "automation partition" and now the "automation folder" are unsuitable in our environment. I'll provide a scenario that's our reality and I don't know if it's been considered from Symantecs point-of-view in regards to a school environment.
Every time the PC is rebooted, this is experienced. Joining a Domain, adding applications/patches/etc.,all requiring reboots, all resulting in this “Windows Boot Manager” displaying for 30 seconds.
In our labs we use a product by Faronics called Deep Freeze which is applied to a “clean image” after deployment. What it does is after a student logs-off, the PC will reboot bringing back a “clean image”. This way any “temp” files/malware/etc. picked-up during their online session doesn’t stay on the system, a “clean image” is always presented to the next user. A computer goes thru countless reboots (logon/logoff) throughout the course of the school day.
We can’t re-educate everyone (over 7000 students/staff/faculty), especially with high turnover with students, that this is a now normal part of the "boot" process, or more importantly, an uninformed student changing the "boot order" causing it to go into automation. This would place an undue stress on IT Support to deal with the amount of “service requests” which would be generated because they think they've become infected because they're not used to seeing this screen or a machine is stuck in "automation" because of a "boot" order change.
With all the difficulty in learning about this new product (coming from 2.5.1)and how to accomplish tasks we’ve been doing over the past 10 years or so, we’ve elected to stay with 2.5.1 (with modded WinPE for newer hardware). Awaiting further advancement of “automation folders” or possible replacement because we can’t move to GSS 3.0 in its’ current state.
Standard Tools WinPE USB question.
I built a USB using the Standard tools Boot wiz, I have a shortcut for Each on the Desk to so I can find them with ease.
When I booted the Command line Black box that opened said : Administrator: DS WinPE4.0 x64 Pre-boot Automation Environment (Disk Boot)
Is this a native Scripting agent or a Symantic Script you recycled.
Just wish to macke sure this corect with it being a WinPE5.1
So far it works.
We have implemented new functionality called automation folders that is the replacement for this functionality. Find more information here:
https://support.symantec.com/en_US/article.DOC9111.html
The only thing to note is that by default this functionality will create a dual boot machine and will show both boot options for 30 seconds on start up. This is default windows behavior and you'll have to change this configuration manually at this time. We're looking to implement a solution for this as soon as possible.
David
Has the VPartition Option been fixed so we can operate as was possible in 2.5, I am not able to PXE boot as it is used by another group to Push out SCCM deployements.
If you have this working I would love to see a video or WebCast on this feature.
Apologies. I'm working on getting this fixed. Thanks for the heads up.
Tried to click on this link to watch the April 22 webcast and the link is broken:
We have finalized our topics for the next webcast and hope you can join us on Wednesday, September 30th. Get more details and sign-up here:
https://www-secure.symantec.com/connect/events/how-webcast-series-ghost-solution-suite-30-september-30
Recording of the June 3rd webcast, slides, sysprep answer file samples, and Q & A are available here:
https://www-secure.symantec.com/connect/blogs/how-webcast-series-ghost-solution-suite-30-june-3rd-recording
Our next "How-to" webcast for Ghost Solution Suite 3.0 will be on June 3rd.
We will demonstrate one recommended practice for creating "gold” images in the enterprise. This will include WinPE driver injection, performing a scripted OS installation, capturing and deploying an image.
Register here: https://www-secure.symantec.com/connect/events/how-webcast-series-ghost-solution-suite-30-june-3
Hi Tomasz,
Thanks for your interest in attending our webinars. We know it's impossible for everyone to attend them either due to time zone or schedule conflicts, so they are all recorded and available for download.
We will hold the one in July earlier in the day and see how that goes with attendance.
Thanks again!
Here are links to listen or download the previous webcasts:
Hello,
Could you schedule your webinars a bit earlier so that people from Europe could also watch the session in their office hours , please ?
Give me a sensible reason why should I stay overtime at work to watch Symantec online session or dedicate my private time.
Thank you.
Tomasz
The recording of the April 22nd "How-to" webcast for Ghost Solution Suite 3.0 is available:
https://www-secure.symantec.com/connect/blogs/how-webcast-series-ghost-solution-suite-30-april-22nd-recording
Please sign-up for our next Ghost Solution Suite 3.0 webcast scheduled for April 22 here:
https://www-secure.symantec.com/connect/events/how-webcast-series-ghost-solution-suite-30-april-22
The recording of the Ghost Solution Suite 3.0 webcast held on March 25 is available here:
https://www-secure.symantec.com/connect/blogs/how-webcast-series-ghost-solution-suite-30-march-25th-recording