I'm deploying a JSD web interface A that should register tickets for our team.
Today, the team receives also tickets via another ticketing tool B.
I would like to know if there is a way to connect both tools, so the tickets received in tool B can be automatically forwarded to the JSD interface A.
Related
On a Kiosk running a Windows PC in a reception area type setting, we would like to run a Microsoft Team Client which can be used to interact with another Teams App (Bot) or a Teams User
We can assign a generic Windows/Azure AD ID so that the Kiosk Windows PC is auto logged in with that ID and then consequently logs into Microsoft Teams with that generic ID (Reception24Kiosk#customer.com for example).
A visitor walks up to the Kiosk. They can then use the already running Teams client to start a chat with the Teams App (bot) or another Teams User.
As Teams client history is persistent, how do we clean up any chat history in the Teams client so that NEXT walk up visitor who uses the Kiosk PC can not see previous chat messages in the Teams client.
We are aware of Teams retention policies and a custom policy could be created for auto deletion but that seems to be measured in number of days. That is too long with this application.
Any way to clear out the chat history on each login to the Teams client (in which case we can somehow force logout the user after each walk up) or another way to reduce the chat history retention to a few minutes?
We have looked at the Microsoft Graph as well, and could not find a way to delete an entire 1:1 chat for a user (even with Delegated permissions)
Any other suggestions from admins who have tried to use Teams in the Kiosk Mode with a generic ID?
Teams client chat history is persistent one. There is no provision to clear out the history on each login. There is Teams retention policy for auto-deletion but as it is measured in number of days, that won't be applicable for your application as you mentioned.
I have an Automation Server where both the Control Room and the clients are installed. The Automation Server is accessed from another Main Server and so the Control Room. I have created some clients in the Control Room from the Main Server. I have logged in to 3 different sessions of the Automation Server and also logged in to the Clients which were created in the Control Room on the Main Server.Now, when i am trying to run a bot from the Main Server, the bot is running on the Automation Server but only in the first client logged in even if i have not selected it. Can anyone help or suggest anything about this issue?
I am expecting to run a bot from the Control Room of the Main Server into the Automation Server into the selected clients.
We want to access our on premises TFS with VSTS CALs. We were trying it with the following information from https://marketplace.visualstudio.com.
We created a user in VSTS with Basic level permissions. It allowed us to create with the email ID of the user. Where as we can not login to the TFS Server with the email ID.
We didn't understand how the VSTS license integrates with our TFS on premises.
Please let us know how we can use VSTS CALs to access TFS Server.
Just as Edward said in the comment, you must first configure your VSTS account have the corresponding access and permission in TFS server.
For example, if you have a domain account company/Ram Datla / Ram Datla#company.com and the user have add in your local TFS server.
For TFS you pay per user for team members who need to use Basic
features like Code or Agile Planning. Team members who have a Visual
Studio subscription are free to add because Basic features are
included in their subscription as a benefit.
If you haven't paid for this Ram Datla#company.com account. You could also be able to access TFS server , however just as a stakeholders, which provides access to a limited set of features. It's also free to add stakeholders to TFS.
If you have paid for the Ram Datla#company.com account with Basic level, then you could also use this account to also have Basic level(who need to use Basic features like Code or Agile Planning) in your local TFS server. Thus you don't have to pay this user again.
Q: Why should I pay via VSTS for my TFS users?
A: You get many benefits, for example:
Paying via VSTS gives your users the flexibility to access both TFS and VSTS for the same price.
You can pay monthly for users who need temporary access.
You get all the purchasing capabilities that Azure offers, like payment via credit card, through a Cloud Solution Provider (CSP)
partner, through the Enterprise Agreement, and more.
Suggest you first go through below links with more detail explain of pricing:
Team Foundation Server Pricing
Buy access to Team Foundation Server
Also take a look at the different Authentication of TFS and VSTS.
My application Connecting to QuickBooks 2013 with QBFC 12.
QuickBooks is running on a Server
Multiple users login to the same server and run QuickBooks from the server at the same time.
Application is also running on the Server.
Application connects to QuickBooks if only ONE user is logged in to the Server and has QB running.
If any other user logs in to the server and opens QuickBooks then the application does not connect.
Message Type: ERROR
Message: The application trying to connect to QuickBooks is not supported while multiple instances of QuickBooks are running.
at Interop.QBFC11.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
at QBFSSyncManager.OpenQBSession()
Message: The application trying to connect to QuickBooks is not supported while multiple instances of QuickBooks are running.
at Interop.QBFC11.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
at Turbo.THUB.QBProcess.QBFSSyncManager.OpenQBSession()
Solution that I found (if it applies to your problem):
If you are running your application from within Visual Studio (any version), make sure VS is NOT running as an Administrator.
This took me hours of hair pulling, name calling, forum screaming and a broken mouse to figure out.
My application works with multiple users, each with separate computers and separate instances of QB, all working in the same QB file via network file share.
I recommend move your application to a separate computer with its own QB instance and open the QB file remotely (not by remote desktop).
A common approach is to move Quickbooks to its own machine , and then write your application such that it receives requests from the other machines. The request can be processed and some sort of message returned. The message can be either a result set or a message letting the caller know if it worked, or if there was a problem.
Without knowing more about what you are trying to do, its hard to give specific advice.
We have recently installed TFS 2010. Our Active Directory users (i.e. my company's staff) can access it just fine.
However, we also have contractors working in the office who do not have an AD account. I am having difficulty trying to get the non-AD users to connect to TFS through Visual Studio. The contractors are on the same LAN but have no AD account, which we do to restrict access to other resources on the network.
I created local Windows user accounts on the server for the contractors. With the local account they can access the TFS web front end but still cannot connect through Visual Studio.
Is there any way to do this? Do the contractors need to have Remote Desktop access to the server itself?
You should definitely give your contractors AD accounts. If you want to restrict access to internal resources, you can use Organisational Units in AD, like
MyCompany
Employees
Contractors
And set access restrictions to your resources according to groups linked to the OUs.
Giving remote access to the server will just create another set of issues.
When you install a non Express version of TFS, you need an AD for authentication, you can't use properly the TFS server from a non AD account.
From this point you have two solutions:
Create AD account for contractors (one per company or one per user, your call).
Create a domain Trust between your domain and the contractor's one. See this documentation for more info.
I don't understand clearly the Remote Desktop part, explain please.