Useful Periodic Citrix EdgeSight Reporting

2017-07-27T00:01:08+00:00 October 27th, 2011|Uncategorized|

I am often asked by customers, “With EdgeSight, what reports should we monitor on a daily, weekly, monthly, or yearly basis?”

EdgeSight is a powerful, but sometimes complex tool.  Based upon my experiences, there are several reports you can schedule to run on a daily basis that will give you a good snapshot of the health of your environment. 

Here is the list of daily reports which I recommend to my customers in order to monitor the health of their XenApp environment:

  • XenApp Summary: XenApp performance data (login time, active sessions, ICA session latency, and CPU and memory usage).
  • XenApp Server Utilization: Average CPU, average memory, and peak concurrent sessions for XenApp servers.  This report contains information about the most heavily loaded servers.
  • Session Client and Server Startup Duration: Average Session client startup duration (CSD) and server startup duration (SSD).  Displays login duration.

By monitoring these three reports, a XenApp administrator will be able to quickly identify if any one of the servers or users has experienced issues over the past 24 hours.  In one instance, the Session Client and Server Startup Duration report was useful in identifying a delay at login that only occurred for the first login after a reboot. 

While you will not necessarily be able to identify a root cause with these summary reports, you will have enough data to begin the troubleshooting process.

SharePoint 2010 – How to move a subsite to a different location

2017-07-27T00:01:08+00:00 October 19th, 2011|Uncategorized|

I had been tasked to reorganize a Microsoft SharePoint 2010 site recently.  One of the things that I needed to do was to move a couple subsites to be under a different parent site within the same site collection.  I researched and was able to find some options, but they all entailed exporting and then importing — or backing up then restoring — the site via command line.

So, I decided to try the export/import method via the command line right on the SharePoint web front end server.  To export the site, these are the steps I tried:

  1. Fire up the command line
  2. CD ”Program FilesCommon FilesMicrosoft Sharedweb server extensions12BIN”
  3. Export the old URL using the following Command:

stsadm -o export -url http://intranet/website -filename c:testbackup.cmp

However, when I tried this under my domain and SharePoint administrator account, I got this error:

The Web application at http://intranet/website could not be found. Verify that you have typed the URL
correctly.  If the URL should be serving existing content, the system administrator may need to add a
new request URL mapping to the intended application.

After searching a bit on this, it seemed like the problem may have been a permissions issue.  So, I confirmed that the administrator account I used had SharePoint Farm Administrative rights, as well as site collection administrative rights.  I then tried to run this same command with a designated “SharePoint Administrator” account which also had SharePoint Farm Administrative rights and Site Collection Administrative rights, but then got an Access Denied error.

After spending some time adding and removing rights for both of those accounts to see if I could get this working, I table the issue and moved on to other tasks.  One of those tasks was to delete some old subsites from our SharePoint.  I ended up stumbling upon the Content and Structure link under Site Administration:

And to my surprise, I found that it is possible to select any site and copy or move it:

  1. Select the parent site of the subsite you want to move in the left navigation pane
  2. Check the box next to the subsite that you want to move in the right pane, click the Actions drop-down and click Move
  3. Then select the destination of the subsite selected in the next dialog box

This method ended up being a lot more straight forward and quicker than the command line option.

I’m glad I found it!

Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113