Thursday, January 03, 2013 2:23 PM
i am using the following setting for central logging of deployments : SLShareDynamicLogging=
Is there also a setting available for the CS.ini for capturing image to centralized logging?
Thursday, January 03, 2013 3:41 PMWhat do you mean by capturing the image to centralised logging? You want to capture the WIM to the same location as the logs, or you want the ZTIBackup.log to appear on the network?
Thursday, January 03, 2013 3:45 PM
i want the log-files when capturing an image available on the network.
Thursday, January 03, 2013 4:36 PM
You probably don't want to use SLShareDynamicLogging in production. that writes the bdd.log to a share in real time, which will cause a lot of extra network traffic when deploying a lot of PCs at once.
Just use SLShare=\\Your Server\your Share.
- Proposed As Answer by JoeZeppy Thursday, January 03, 2013 4:37 PM
Thursday, January 03, 2013 8:15 PM
dynamic logging works fine at my environment.
Do you also know that command for logging the capture-process on the same way?
Friday, January 04, 2013 7:38 AMIs there an option available for logging the capture-process to a central location like "SLShareDynamicLogging" for the deployment of an image?
Saturday, January 05, 2013 8:33 AMAnybody with an option for central logging of the capture-process?
Saturday, January 05, 2013 4:17 PM
I'm not sure I understand what you're looking for? SLShareDynamicLogging takes a copy of the bdd.log to a network location in real time.
I'd have to look Monday at work, but I think I use SLShareDynamicLogging =\\server\share\%OSDComputername%
Saturday, January 05, 2013 4:35 PM
with SLShareDynamicLogging with a deployment the bdd.log is saved central!
But when i do a CAPTURE ths bdd.log is logged to the client and not central!
Saturday, January 05, 2013 8:24 PMYou can absolutely use SLShareDynamicLogging also when building the image, i.e. doing the capture.
Blogging about Windows for IT pros at www.theexperienceblog.com
Saturday, January 05, 2013 11:02 PMYes, exactly. a task sequence is a task sequence, doesn't matter if you are building a reference image or deploying it to a user.
Sunday, January 06, 2013 8:57 AM
my setting for SLShareDynamicLogging is provided in the cs.ini.
The result at this moment is that deployment bdd.log-files are saved on the deployment-server, and bdd.-log-files for a capture-process are saved locally.
Do I need to customize my configuration (capture-tasksequence?) or something?
Monday, January 07, 2013 1:42 AMI would check the log on the capture side to see if there is a reason it isn't going to the network. Perhaps your capture process build account doesn't have rights to the share? If you are not specifying a separate location somehow, it should all go to the same place.
Monday, January 07, 2013 7:18 AM
this is the content of my sysprep_capture task-sequence:
There are no other credentials applied when running this task-sequence...
Monday, January 07, 2013 7:52 AM
I have started a capture-process amd checked the log-file (that is local on the client and not on the server):
This indicateds the settings that are applied from the cs.ini
But the result is that the bdd.log is saved locally!
How to fix this?
Monday, January 07, 2013 9:28 AMthe logs are still saved locally but are also copied to the network share if i remember correct
Monday, January 07, 2013 9:35 AM
i did a test with:
SLShare : bdd.log and other files are copied from local to network after deployment/capture
SLShareDynamicLogging : log-files are live available on network during deployment, and not by doing a capture.
Can you test/confirm this?
Monday, January 07, 2013 10:49 AM
i Captured an image with BOTH settings in cs.ini
slShare : all files are copied after capture the the specified folder
SLShareDynamicLogging : nothing happens
So for capture-process only slshare seems to work?
I have test this on 2 different Deploymentshares with MDT 2012 Update 1.
Can somebody test this, and confirm?
Monday, January 07, 2013 8:37 PM
you should be using Trace32 to read logs, its much easier to see where errors are occurring. This is showing that the variable is getting set, have you looked farther down to see if you are getting any errors when the logs are being written?
Tuesday, January 08, 2013 7:23 AM
i am using trace32 already.
There are no errors, and the path is set for both variables to the network, but only slshare is used by capturing a image.
Can somebody test and confirm?
Tuesday, January 08, 2013 5:54 PM
Your screen shot shows Notepad. Not sure what you want us to test. I'm running my build and capture reference PC task right now, and it is logging to my network share fine. If you are talking about the exact point in time where it is creating the WIM, I havent gotten that far yet.