![]() ![]() ![]() The following example PowerShell script could be run to start collection: Start IntelliTrace Collection on an Application Pool Note that you can exit the session with Exit-PSSession. WinRM is not set up to allow remote access to this machine for management.Ĭreate a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machineĪfter this has been done, you will be able to enter remote PowerShell sessions on the server with a command like this:Įnter-PSSession -ComputerName COMPUTERNAME WinRM already is set up to receive requests on this machine. To enable remote PowerShell on the server machine, you (or someone) must run WinRM QuickConfig from an elevated command prompt and say yes when prompted to enable a firewall exception: The primary advantage of a remote PowerShell session is that it carries much less overhead, since it saves your server the trouble of spinning up UI. Note also that expanding in the Windows shell does not preserve the proper directory structure of these files. # This would be run on the server, or via a remote PowerShell sessionĬopy-Item $SharePath* -Destination $StartingDir -Recurse $CabFilePath=”$VSPath$IntelliTrace11PathIntelliTraceCollection.cab” $IntelliTrace11Path=”CommonExtensionsMicrosoftIntelliTrace11.0.0″ $VSPath=”C:Program FilesMicrosoft Visual Studio 11.0Common7IDE” Net use $SharePath $Password /User:$Username # This would be run from your client machine I’m assuming here that you are running on a dev machine with Visual Studio Ultimate installed to the default location: These may not be best practices for your environment, but if you want to script them, here are some samples. cab file to a share on your server machine from your client machine, or to a mutually-accessible share from which you can copy files to your server via a remote session. You may wish to run this while logged in to the server. Note: I get an error if I try to run this through a remote PowerShell session. Note that this file will be located under the x86 Program Files directory at Microsoft Visual Studio 11.0Common7IDECommonExtensionsMicrosoftIntelliTrace11.0.0, or can be downloaded from MSDN (Microsoft Visual Studio 2012 Release Candidate here):Įxpand IntelliTraceCollection.cab -f:* C:IntelliTraceCollection Expand IntellitraceCollection.cab to your collection folder through a command like the following. $Rule=New-Object ($Principal,$Right,”Allow”)ģ. New-Item -Path $Drive -Name $FolderName -Type Directory Steps 1-2 can be run using a PowerShell script like the following, and if you have the right permissions, there is no reason you couldn’t also run this remotely, as described below: Grant write access for the folder to BUILTINIIS_IUSRS.Create a folder on your server machine (assumed below to be C:IntelliTraceCollection).Stop IntelliTrace Collection on an Application Pool.Start IntelliTrace Collection on an Application Pool.Set Up an IntelliTrace Collection Folder.My goal is simply to provide some initial examples that you can modify to suit your needs. The IntelliTrace Standalone Collector is free for anyone to download (find the Microsoft Visual Studio 2012 Release Candidate here), but opening the logs requires Visual Studio Ultimate.ĭisclaimer: I am not an expert with PowerShell, so some of this code may violate best practices or otherwise reveal my naïveté. General information about IntelliTrace collection with the Standalone Collector can be found here (MSDN), or you can watch this video from Tech Ed 2012. This post will specifically provide some example scripts that may be helpful if you want to collect IntelliTrace information on your server via a remote PowerShell session. a production server) and analyze the log on another machine (e.g. The Standalone Collector allows you to collect IntelliTrace logging information on one machine (e.g. This post pertains to the IntelliTrace Standalone Collector, a new feature associated with Visual Studio 2012. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |