MiShare website retirement FAQ Page


Question

What scenarios may come up with the decommissioning of the https://mishare.med.umich.edu webpage on 12/15? 

Answer

Scenario 1

Issue: I was using https://mishare.med.umich.edu to send or receive an ad-hoc package.

Answer: You can use the following alternatives

1. Dropbox

*ITS Dropbox is supported by the ITS Helpdesk. For specific help or issues, please use this webpage: https://its.umich.edu/help

2. Microsoft OneDrive

3. Encrypted email

*Can be used for file attachments under 25 megabytes. To enable, use the [SECURE] tag in your outbound Outlook email message. 

 

Scenario 2

Issue: You are having a password issue. 

Answer: A ticket to the Enterprise Clinical Support team should be entered to follow up. They will need to provide you with a system-generated password for your use moving forward. 

 

Scenario 3

Issue: I'm a b2b customer and I need to push or pull files

(b2b means business to business. It’s an account to push or pull data to or from Michigan Medicine. It is designed for shared use by one area, as opposed to one individual.)

Answer: You will now need to use an SFTP program such as FileZilla. The instructions are here: FileZilla Instructions.docx

 

Scenario 4

Issue: I'm a b2b customer and I'm unable to log in/connect

Answer: A ticket to the Enterprise Clinical Support team should be entered to follow up

 

Scenario 5

Issue: I need access to view my home directory or shared folders I have access to

Answer: You will now need to use an SFTP program such as FileZilla. The instructions are located here: FileZilla Instructions.docx

 

Scenario 6

Issue: You would like to establish a new b2b account or automated transfer.

Answer: A ticket to the Enterprise Clinical Support team should be entered to follow up. It will need to be approved for escalation to the CISO using a Risk Decision Request.

 

Scenario 7

Issue: You would like to modify an existing b2b or automated transfer

Answer: A ticket to the Enterprise Clinical Support team should be entered to follow up. As long as the endpoint is not net new, we should be able to follow up accordingly.

 

 

 

For further information, please bookmark the following page for ongoing updates: MiShare replacement project website