G
Guest
Server is 2003 W/SP1. RIS images are Windows XP SP2 with all microsoft
updates. The errors on the imaging service have been isolated to the latest
Symantec Enterprise client. Images with the older version of Symantec work,
they fail on the newer version of Symantec.
When we used the client version of Symantec 10.0.2, we were able to
push up images to the RIS service, and pull them back down, automatically
joining the domain, and without sharing violations.
We are creating a new image using the latest Symantec client. There is a new
service that has tamper protection on it; SPBBCSvc.exe. When pushing up this
image, there are file sharing violation errors, and when pulling down this
image it will not join the domain automatically. Anyone else run into this?
Below is a copy of some correspondence we have had so far.
I spoke to Symantec support staff about this.
1. The tmp files are being created because Real Time Protection is scanning
a file at the time. i.e. SAVCE is using those files and that is the source of
the sharing violation. I suggest that they disable Real Time Protection and
stop the Symantec AntiVirus service. Then, clean up all tmp files on the
source drive.
2. The SPBBCSvc.exe file is associated with Tamper Protection and Symantec
does not provide a way to disable this.
3. Symantec recommends not pre-installing SAVCE to the image but having it
installed silently after first boot of the installed image. This is how the
majority of customers that I have worked with before accomplish this task.
Please see the following KBs for general guidance:
Title: 'Configuring Symantec AntiVirus for deployment as part of a drive
image'
Document ID: 2005092215503348
Ø Web URL:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005092215503348?Open&src=w
Title: 'Image with installed Symantec AntiVirus 9.x or 10.x client prepared
with Sysprep cannot join a network domain'
Document ID: 2004052710203048
Ø Web URL:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2004052710203048?Open&src=w
Conversation: SAV 10.1.0.394
Subject: SAV 10.1.0.394
To Whom It May Concern:
Attached are the file(s) as requested per the problem listed below…
When capturing the baseline image for Fort Carson with SAV installed on the
image using Remote Installation Services from Microsoft we receive a sharing
violation error copying the file “C:\Program Files\Symantec Anti
Virus\SAVRT\0199NAV~.tmpâ€. We click Retry and the process continues to copy
the rest of the image to the server. The problem comes when we try to
automatically join the domain in mini setup using a riprep.sif answer file.
When mini setup comes to the point of joining the domain an error comes up
“Domain could not be accessed due to networking problems…†That error is
common with network drivers not loading or credentials not being passed
through. However, when continuing in a workgroup the domain can be joined
with no problem.
Also, the service SPBBCSvc.exe is giving us problems when we try to stop it.
When I run a taskkill command it says the process is stopped but Task
Manager and the riprep GUI still show the service as running. We tried to
disable the service and rebooting to keep it from starting altogether.
However, we still receive the same error.
Note: During testing using the same process, the image could be deployed and
joined to a domain in mini setup with no problem when SAV 10.0.2.2020 was
included in the image.
updates. The errors on the imaging service have been isolated to the latest
Symantec Enterprise client. Images with the older version of Symantec work,
they fail on the newer version of Symantec.
When we used the client version of Symantec 10.0.2, we were able to
push up images to the RIS service, and pull them back down, automatically
joining the domain, and without sharing violations.
We are creating a new image using the latest Symantec client. There is a new
service that has tamper protection on it; SPBBCSvc.exe. When pushing up this
image, there are file sharing violation errors, and when pulling down this
image it will not join the domain automatically. Anyone else run into this?
Below is a copy of some correspondence we have had so far.
I spoke to Symantec support staff about this.
1. The tmp files are being created because Real Time Protection is scanning
a file at the time. i.e. SAVCE is using those files and that is the source of
the sharing violation. I suggest that they disable Real Time Protection and
stop the Symantec AntiVirus service. Then, clean up all tmp files on the
source drive.
2. The SPBBCSvc.exe file is associated with Tamper Protection and Symantec
does not provide a way to disable this.
3. Symantec recommends not pre-installing SAVCE to the image but having it
installed silently after first boot of the installed image. This is how the
majority of customers that I have worked with before accomplish this task.
Please see the following KBs for general guidance:
Title: 'Configuring Symantec AntiVirus for deployment as part of a drive
image'
Document ID: 2005092215503348
Ø Web URL:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005092215503348?Open&src=w
Title: 'Image with installed Symantec AntiVirus 9.x or 10.x client prepared
with Sysprep cannot join a network domain'
Document ID: 2004052710203048
Ø Web URL:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2004052710203048?Open&src=w
Conversation: SAV 10.1.0.394
Subject: SAV 10.1.0.394
To Whom It May Concern:
Attached are the file(s) as requested per the problem listed below…
When capturing the baseline image for Fort Carson with SAV installed on the
image using Remote Installation Services from Microsoft we receive a sharing
violation error copying the file “C:\Program Files\Symantec Anti
Virus\SAVRT\0199NAV~.tmpâ€. We click Retry and the process continues to copy
the rest of the image to the server. The problem comes when we try to
automatically join the domain in mini setup using a riprep.sif answer file.
When mini setup comes to the point of joining the domain an error comes up
“Domain could not be accessed due to networking problems…†That error is
common with network drivers not loading or credentials not being passed
through. However, when continuing in a workgroup the domain can be joined
with no problem.
Also, the service SPBBCSvc.exe is giving us problems when we try to stop it.
When I run a taskkill command it says the process is stopped but Task
Manager and the riprep GUI still show the service as running. We tried to
disable the service and rebooting to keep it from starting altogether.
However, we still receive the same error.
Note: During testing using the same process, the image could be deployed and
joined to a domain in mini setup with no problem when SAV 10.0.2.2020 was
included in the image.