Something on my computer is randomly calling a couple SharePoint sites. The last time the mystery process ran, it made 20K calls to a couple different SharePoint sites.
I tried closing Outlook, OneNote, Designer, and other apps that were running. No Task Schedules are set to run around the time this happened.
Using Fiddler, is there a way to identify what is making a call to a site?
Look at the Process column to find out what process is issuing the request. You will likely either see one of the Office applications (which periodically refresh a registry-based list of SharePoint sites you've used) or a svchost.exe instance. If it's a svchost.exe instance, you'll need to use a tool like Process Explorer (or the Win8+ Task Manager) to see which services are running within the svchost.exe with the specified process ID.
Related
I am a network admin with very little experience coding or using Powershell. About once a month I have to check for and install Windows updates on about 25 servers. I've played around with Powershell in hopes of handling this task in a more automated fashion but get hung up getting the servers to actually install the updates after checking. I apologize for posting such a noob question, but can anyone let me know if this is possible and if so, show me the ways of your dark arts?
WSUS will require you to install the components and setup the profiles etc. If you have a large number of servers on a single network, that is your best bet for delivering the content.
If you just want to be able to schedule and run the updates on specific remote hosts, there is a ton of stuff already available that will do this and you just need to come up with your implementation of scheduling the updates for what hosts. I did this exact thing for a prior employer for 10k plus servers world wide using a web app for the owners to schedule the updates and then back end workflow to perform the approval requests, installs, logging, etc..
PowerShell Gallery is a good start. Here is a post that walks you through using PSWindowsUpdate.
I'd appreciate help determining why my Word VSTO Add-In is causing 45 second load times.
The Add-In is used by multiple customers, only one of which experience this issue. I can not reproduce the problem on any of my test environments. (all running Windows 10, Office 365)
Findings:
v35 of the Add-In works fine (built back in March).
After the customer installs v55 the problem starts (built in July).
I've incrementally removed all my code, nuget packages, reference (everything) from the Add-In and the problem persists.
I've removed my Add-In and create a new WordAddin1 project. The 45 second problem occurs when this Add-In is installed at the customer.
If I rebuild v35 today and run on the customer machine it works fine.
I have established that the 45 seconds happens BEFORE my Add-In code get's a chance to run.
I have run fuslogvw.exe to determine if any dependencies are causing timeouts (they aren't)
I have run performance monitoring to ensure that CPU, Memory, Disk, Network traffic are at acceptable levels (they are)
I have run Telerik Fiddler to monitor traffic and can see multiple calls (4) to Windows Update that time out (the customer pushes out updates via SCCM and does not get updates from Windows Update)
2 of those Windows Update calls and timeouts happen when I disable my Add-In and Word opens within 5 seconds.
How can I better understand what Word is doing during that 45 seconds? It's a black box that I can't seem to peer into.
Any help greatly appreciated
Is it possible to get Dell KACE to run a script on a client machine immediately when some condition happens?
I need the script to run on the agent machine within 1 minute of the condition happening (like a file appearing). This is because I need an application to update to a newer version only when a user action happens.
If I set the inventory interval very low and use a custom condition it might affect the general performance of KACE, since there are many client machines.
It's impossible to do this.
I can send an inventory via the API even without admin rights. But the inventory checks/results cannot be linked to scripts in KACE, so that gets me nowhere.
Using Fiddler, I want to send multiple requests in one hit, to check the response time from the server, if too many requests are sent at one time. Basically, I want to perform a, kind of, load testing on my service. Is there any way to perform this action? I want to repeat the process of hitting the server, again and again.
In Fiddler, you can repeat a request as many times as you like by hitting SHIFT+R on the selected Web Session. You'll be prompted for a repeat count and then Fiddler will issue the specified number of requests.
Caveat: Having said that, generally speaking, you'd want to use a tool like Telerik Test Studio's Load Test tool for a task like this. Alternatively, you could use Fiddler's Export architecture to generate a script for VS WebTest or Microsoft's free WCAT tool and use those tools to generate the load. You can then run these scripts on multiple machines from multiple networks and generate a more-realistic set of load than you could by simply running on a single client.
I've been load testing with StresStimulus today. Overall, I'm quite impressed.
It's now a standalone application (it used to be a fiddler extension). There's a 7 day free trial which allows up to 50 virtual users. Also, the setup wizard is great for beginners.
For basic load testing the trial should be fine. Consider upgrading for extensive/professional use.
I want to write a workflow application that routes a link to a document. The routing is based upon machines not users because I don't know who will ever be at a given post. For example, I have a form. It is initially filled out in location A. I now want it to go to location B and have them fill out the rest. Finally, it goes to location C where a supervisor will approve it.
None of these locations has a known user. That is I don't know who it will be. I only know that whomever it is is authorized (they are assigned to the workstation and are approved to be there.)
Will Microsoft Windows Workflow do this or do I need to build my own workflow based on SQL Server, IP Addresses, and so forth?
Also, How would the user at a workstation be notified a document had been sent to their machine?
Thanks for any help.
I think if I was approaching this problem workflow would work to do it. It is a state machine you want that has three states:
A Start
B Completing
C Approving
However workflow needs to work in one central place (trust me on this, you only want to have one workflow run time running at once, otherwise the same bit of work can be done multiple times see our questions on MSDN forum). So a central server running the workflow is the answer.
How you present this to the users can be done in multiple ways. Dave suggested using an ASP.NET site to identify the machines that are doing the work, which is probably how I would do it. However you could also write a windows forms client that would do the same thing. This would require using something like SOAP / WCF to facilitate communication between client form applications and the central workflow service. This would have the advantage that you could use a system try icon to alert the user.
You might also want to look at human workflow engines, as they are designed to do things such as this (and more), I'm most familiar with PNMsoft's Sequence
You can design a generic "routing" workflow that will cause data to go to a workstation. The easiest way to do this would be to embed the workflow in an ASP.NET application. Each workstation should visit the application with a workstation ID in the querystring:
http://myapp/default.aspx?wid=01
When the form is filled out at workstation A, the workflow running in the web app can enter it into the "work bin" of the next workstation. Anyone sitting at the computer for which the form is destined will see it appear in their list of forms to review. You can use AJAX to make it slick and auto-updating.