Find out who’s logged on to a Remote Desktop Session


andrewlocatelliwoodcock

It’s a problem I’ve hit multiple times: I need to remote into a server to do some work but there are only a few sessions available and they’re all in use. I could ask someone if they can log off for a while but as it’s possibly one of a number of people this requires a bulk email. What I really need is a way to identify exactly who is logged onto that server so I can ask them if they can log off for a while …

After a fair amount of googling, I tracked down the query session command for Windows which will do exactly this. Here’s an example:

query session /server:[SERVERNAME]

where [SERVERNAME] is the name of the server you are trying to remote onto. So if we were trying to connect to a server named MyServer, we’d enter:

query session /server:MyServer

Here’s redacted example of the…

View original post 50 more words

1984


jdubqca


nobody cares about nineteen
eighty-four anymore

nobody seems to remember
how lovely the wine tasted
nor how the hash under glass
made the world such a
beautiful place

there is no rewinding
there is only nineteen eighty-four
when the world mushroomed
and there were no more
children to be born

some say the final war
brought lasting peace
to this world

but nobody can be sure


november two thousand thirteen
copyright j matthew waters
all rights reserved

View original post

Getting documents from a #FHIR XDS infrastructure


Hay on FHIR

So far in our little mini series on FHIR and XDS we’ve had an overview of how FHIR resources support a document sharing infrastructure, looked at how a document creator can create and submit documents to a repository and/or registry, and spent a bit of time talking about the DocumentReference resource.  Time to think about the consumer of these services.

There are 2 main scenarios that we want to support:

  • Getting a list of documents for a patient (with various search parameters – e.g. a date range, type of document etc.) and displaying the metadata in a list to the consumer
  • Retrieving a particular document to view

Getting the list of documents

Let’s think about the first scenario, and to keep it simple we’ll aim to retrieve all the documents for a patient. Given that the metadata about the document is represented by a DocumentReference resource hosted by the registry…

View original post 942 more words

Nov 19th Chat – Disclosures for Tweet Chats – The Good, Bad and Ugly


#hcldr

hcldr

Disclosure SummitIntro by Colin Hung

This week on #HCLDR, we are excited to welcome Matthew Katz (@subatomicdoc) and Patricia Anderson (@pfanderson) as guests.

Matthew has been working on an interesting initiative called #HLTHTOP – where tweets and other resources are categorized so that it is easier for patients, caregivers, providers and researchers to find information. The initiative focuses on the use of tagging content via hashtags (something all of us who use Twitter are familiar with).

When these tags emerge spontaneously, they are part of a folksonomy – user-generated organization.   Spontaneous hashtags are fine to highlight a meeting, but when discussing a specific disease I believe there is value in an organized system for reliability and consistency.  So I proposed a cancer tag ontology, a top-down system which I have shared on Twitter based originally up #bcsm, a robust breast cancer community.  With the…

View original post 844 more words