CTX Driver
Use the standard 'Print' command in almost any application to create a PDF and save it directly to ShareFile. This is particularly useful for business systems such as EMR or practice management where secure sharing is required and saving a copy of the document to your computer could create compliance issues. Then install Oracle Client libraries and you're ready to go! See Godror Installation for more information. To connect to Oracle Database use sql.Open('godror', dataSourceName), where dataSourceName is a logfmt-encoded parameter list. Jan 07, 2020 This driver supports the ColumnType interface introduced in Go 1.8, with the exception of ColumnType.Length, which is currently not supported. Context.Context Support. Go 1.8 added database/sql support for context.Context. This driver supports query timeouts and cancellation via contexts. See context support in the database/sql package for. Conn (ctx) // Set us up so that temp table is always cleaned up, since conn.Close // merely returns conn to pool, rather than actually closing the connection. Defer func = conn. ExecContext (ctx, 'drop table #mytemp') // always clean up conn.
- Provisioning Services
Symptoms or Error
This article provides information about how to troubleshoot a target device that fails to boot into a vDisk. The status of the target device appears as a red X state within the console
Solution
Complete the following steps to resolve the issue:
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
IP Aquisition
Verify DHCP/PXE/TFTP services are running successfully in your environment:
This can be verified using the CTX217122 - PXEChecker for Citrix Provisioning ServicesValidate that Network boot is enabled in BIOS.
Disable Spanning Tree Protocol or enable Port Fast on any port the switch uses for PVS traffic.
Note: Refer to CTX117374 - Best Practices for Configuring Provisioning Services Server on a Network for more information on firewall settings.
- Enable Verbose mode under the bootstrap.
When the target device boots, verify that it is getting an IP address while connecting to the TFTP server.
Note: In the screen shot, the target device is trying to boot through the Boot Device Manager (BDM), while the TFTP protocol is downloading tsbbdm.bin instead of ardbp32.bin.
- Run the following tftp command to test TFTP from the target device to the PVS server:
tftp <IP of the TFTP server/PVS> get ardbp32.bin
Note: Test TFTP by installing the TFTP protocol in Windows 7 with Add Remove Windows Features, and with Windows 2008 in the Add Features server role.
In a broadcast domain, only one PXE server can be configured. Some environments might have another third party software running the PXE protocol, such as Norton Ghost.
Note: When using DHCP scope options, the PXE server does not need to be configured in an environment.
- If PXE or DHCP options fail to boot a device, configure a BDM file to test boot a target device. Configure BDM with a static IP address and it will bypass the DHCP Server..
On the server and target device, the following ports are used:
If you are using a virtual machine, validate the Network Interface Card (NIC) used to connect to the PVS server at the top of the list containing the polling order of network cards.
For the Stream service: UDP 6910, 6911, 6912, 6913, 6914, 6915, 6916, 6917, 6918, 6919, 6920, 6921, 6922, 6923, 6924, 6925, 6926, 6927, 6928, 6929, and 6930.
For the console: TCP 54321 and 54322. TFTP: Port 69.Disable the Windows Firewall on the target device and server. After verifying the firewall, open the ports: UDP 6890 – 6909 for communication between servers.
Note: Refer to CTX117374 - Best Practices for Configuring Provisioning Services Server on a Network for more information on firewall settings.Uninstall the Antivirus software. After the target device boots, install the Provisioning Services (PVS) target software in private image mode.
Note: Refer to CTX124185 - Provisioning Services Antivirus Best Practices for more information on configuring Antivirus software.Verify you are able to ping the target device to the PVS server.
Note: Use the IP address of the server rather than the Fully Qualified Domain Name (FQDN).- Disable IPv6 on the server and target device by editing the registry and modifying the following key:
HKLMSYSTEMCurrentControlSetServicesTcpip6Parameters
DWORD DisabledComponents = 0xff
Image Creation
Remove hidden network cards from Device Manager. (Note: Do not remove hidden (ghost) Network Cards from a XenServer target. Only remove them from Hyper-V, VMWare or Physical targets)
Note: Refer to CTX133188 - Event ID 7026 - The following boot-start or system-start driver(s) failed to load: Bnistack for details on how to remove hidden network cards.Uninstall any software on the target device that configures a third party NIC driver, such as IBM Tivoli.
If the target device or PVS Server is configured with bonded network cards, break the bond and test with only one NIC active.
This will simplify the environment and validate if the bonding network cards could be causing an issue.
Note: Refer to Requirements and considerations for manufacturer's NIC teaming.- If the environment is configured with vSphere 5.0 (without any updates) and using VMXNET3 drivers, either enable Interrupt safe mode in the bootstrap or upgrade to vSphere 5.1 or later.
Note: For additional information, refer to CTX131993 - vSphere 5 Support for Provisioning Server 5.6.x, 6.x and 7.x.
Additional Resources
- CTX117374 - Best Practices for Configuring Provisioning Server on a Network
- CTX123638 - Error: “Connection to Provisioning Services. Please wait…” Appears when Attempting to Boot using BD
- CTX119000 - vDisk Inactive State with Broadcom Network Cards
- CTX132133 - Provisioning Services 6.0 Targets Stop Responding at a Black Screen
Disclaimer
System Requirements
- Windows 7 or later
- Microsoft .NET Framework 4.5 Click here for information on updating .NET
- Versions 2.8 or higher support the TLS 1.2 Security Protocol see, ShareFile TLS Guidance for more information.
Limitations
- Print to ShareFile will not appear on the Apps page for Client users. If you wish to download this app, you may submit requests directly by clicking here: https://www.sharefile.com/support
- This feature has not been tested with single sign-on or virtual environments.
- Modifying the name of the printer will cause this feature to malfunction.
- When uploading a PowerPoint file, it will be saved as a PDF file with one slide per page.
- When uploading an Excel file, it will be saved as a PDF file with roughly 40-45 rows per page.
Instructions
Print to ShareFile also allows you to send a file for signature using RightSignature, or Fax with ShareFile via SFax.
Install
To install this feature, log in to your ShareFile account and navigate to the Apps section. Locate Print to ShareFile in the list and click the Download button to download the installation file. Once the file has been downloaded, run the installation file and proceed with setup. You must accept the License Agreement to continue. After installation, Citrix Print to ShareFile will automatically be added to your Devices and Printers.
Use Print to ShareFile
Once the ShareFile Print driver has been successfully installed, you may use the Print function to save a document as a PDF directly to your ShareFile account. To do, access the Print option from within the document you wish to save. For most file types, click File and Select Print. If it is your first time using Print to ShareFile, you may need to select Citrix Print to ShareFile as your designated Printer in the Print options menu of your document. Once you have chosen Citrix Print to ShareFile as your printer, click Print.
Do I have to sign in every time I use Print to ShareFile?
No. Once you have logged in with ShareFile credentials, the Print to ShareFile app will remember your login information. To sign in as a different user, use the Unlink This Account option.
Choose an Upload Destination
Once your account credentials have been verified, you may alter the name of your file and select the Folder you wish to upload your document to. This action requires upload permissions on the specific folder. You may also create and name a new folder by clicking the Create Folder button after selecting a folder where you have upload permissions. You cannot select Shared Folders or Favorite Folders as an upload destination because they are root-level folders. Once you have chosen your upload destination and named your file, click Upload Only. Your file will be uploaded to your ShareFile account as a PDF document.
More Options
The More Options drop-down menu allows you to share your file in addition to uploading it to your account. You can share your file via the ShareFile email, generate a link to your file that you can copy and paste elsewhere, send your file as an encrypted email message, or send your file out for signature using RightSignature.
Share via Print to ShareFile
You may share a copy of your file using the More Options drop-down menu. To do so, access the More Options drop-down menu and choose how to share your file. You may enter your recipient and customize your message options as needed. If you are sending to a recipient located in one of your ShareFile Address Books, the email or name will recommend the user.
Email with ShareFile
Copy a Link
Encrypted Email via Print to ShareFile
This option is only available to users with the Encrypted Email feature.
Using Print to ShareFile with View-Only Sharing
Accounts with View-Only Sharing enabled may share files as view-only, as well as customize the relevant options before sending the message.
Print to ShareFile - Send for Signature with RightSignature
Users with the RightSignature integration enabled on their account can send a file for signature from the Print to ShareFile app.
To do so, print your file to ShareFile as you normally would. Select an Upload destination. Next, access the More Options drop-down menu and select Send for Signature.
If an upload destination is not selected before choosing Send for Signature, your file will be uploaded to the My Files & Folders section of your account.
Once your file has been sent for signature, you will receive a confirmation message. Your file will open in a new browser window. Verify your RightSignature credentials if prompted. Next, customize your file with a signature field and send it to the necessary recipients as you normally would. You can check on the status of your file in the ShareFile web app.
Fax with ShareFile - Fax a Document with Sfax
Ctx Driver Golf Clubs
Note: This feature requires Print to ShareFile version 2.3 or later and an Sfax account.
To fax with ShareFile via Sfax, print your file to ShareFile as you normally would. Select an Upload destination. Next, access the More Options drop-down menu and select Send with Sfax.
Tx Driver License Eligibility
You must enter your Sfax connection info, including Username, API Key, and Encryption Key. In order to utilize the Sfax integration, the Admin of your Sfax account must have activated the ShareFile integration and provided users with their API and Encryption keys. If you have not received your API or Encryption Keys, please contact your Sfax admin.
Check 'Save this Information' so Print to ShareFile will not prompt you for this information the next time you fax to sharefile. Once you have entered the required information, click Continue.
Before sending your fax, designate your recipient and customize your message as needed. Note: Option fields may be dependent upon default settings configured in Sfax. If you do not see a setting, please contact your Sfax administrator.
Tx Drivers License Renew
When you're ready, click Send Fax to send your message. A copy of your fax will be automatically uploaded to your ShareFile account.
Tx Driver's License
Using Print to ShareFile with XenApp
Tx Drivers License
Print to ShareFile version 2.0.251.0 and later may be used in a published XenApp desktop environment. In order to use Print to ShareFile in a published application environment, certain modifications must be made to your XenApp server. User profiles that exist on the XenApp server but were not originally created by launching a published desktop will need to be deleted from the XenApp server in order to use the workaround. Attempting to do so without making necessary changes will result in the Print to ShareFile application failing to launch outside of the desktop session.