ROn - collecting Repro-On data / log(s), required for below options unless -+ is present. SrvOn - generate SMB/NFS/DFS server component ETL log(s) Usage: TSS + see below sections ' Additional module options:' -and 'Predefined Tss scenarios:'Īt least one of *on: cliOn, srvOn, rOn (= ReproOn) or any predefined must be specified.ĬliOn - generate SMB/NFS client component ETL log(s) TSS rOn cliOn Trace Video - enables SMB-client ETL log(s), Network sniff=Trace, Problem-Step-Recorder, Video and SDP report Usage examples: TSS General - enables general purpose log(s), DNScli, Network sniff, PSR, SDP, wait for user input w/ ANY-key Syntax: Tss Param argument in for Param is optional, defaults will be used if argument is missing, the order of sub-args is mandatory, '|' means 'OR', ':' is a delimiter between params and/or args, 'def: val' stands for Default value, '' in angle brackets is placeholder. TSS has been developed and maintained by Microsoft Support Platform Escalation Team.
) to collect static (like Event Logs, registry outputs, configuration outputs and similar) or dynamic repro logs (like network traces, user/kernel mode memory dumps, perfmon logs, Process monitor logs, ETL traces from various Windows OS components and similar) to troubleshoot various Windows OS or other Microsoft product related problems dispatched to Microsoft Support. TSS is a collection of cmd/powershell scripts that mainly utilize the built-in Windows OS logging mechanisms or other Microsoft tools (like process monitor, procdump. ) to collect static (like event logs, registry outputs, configuration outputs and similar) or dynamic repro logs (like network traces, user/kernel mode memory dumps, perfmon logs, Process monitor logs, ETL traces from various Windows OS components and similar) to troubleshoot various Windows OS or other Microsoft product related problems dispatched to Microsoft Support. I have been watching a few GC videos on Youtube but I must admit I not familar with what all the charts mean.TSS is a collection of cmd/powershell scripts that mainly utilize the built-in Windows OS logging mechanisms or other Microsoft tools (like process monitor, procdump. That should get easier as I am recovering from a broken wrist and should start to put in at least one outdoor ride a week shortly. Therefore I am just focussing on TSS for each week and trying to hit between 350 and 450 weekly. I want to get my CTL to over 50 before spring and I have no race planned until at least April so no concerns at the moment. I don’t understand why it starts at 0 but I didn’t do much through the summer. It is clear that I am growing my CTL – now at 31.5 and I am probably reasonably tired.
My PMC chart for the last two months from Golden Cheetah is shown below I deleted them and the mass upload went well.
I then realised that within the zip file from Strava were a lot of tcx files with 0 bytes. One problem I had was that the load would get stuck and hang, sometimes even on only a single file.
I then installed Golden Cheetah and imported all my files (which come from Strava as a mass download). I did have a Excel spreadsheet where I have entered all my workouts since 1/1/16 and that gives me a current CTL of about 42. With having used the turbo exclusively for the last 3 months I wanted a good way of measuring the effort I have been putting in. I am also interested in following my TSS numbers as a means of managing weekly effort, rather than focussing on mileage. I could probably get my 5s a bit higher but I think 823 is probably unreachable and I am not even going to try. I have put in how many watts I need to get the lowest ranking for a man – and that makes me untrained. I cannot even get on the page for 5s and 1M but I do have the right shape for the other two.