Re: Free Download Excel Image Assistant Full Version
Katerine Aldrige
Hi@buddj83 ! Looks like you and I are left in the cold. HOWEVER, I did discover a workaround that has helped: Below the ribbon at the top is a beige band that states, "Security Warning..."Enable Content" -- Once I clicked "Enable Content", and REDID the link...that seem to work. I don't know if that's a permanent solution...but hope it helps.
Thankfully, I was able to create a Microsoft 365 and PowerApps Savant to assist me in situations like these. I have decided to forego the IMAGE() formula based on the response received from ChatGPT. Currently I run a VBA code to insert and embed the images as an object and it works perfectly for my needs. Here is the response I received from the Savant:
"The #BLOCKED! error message in Excel indicates that the image could not be loaded due to security settings or network restrictions. This error message is usually caused by the security settings of your computer or network, which might be blocking the image from being loaded.
It is worth noting that using the IMAGE() formula to insert images in Excel can cause the file size to become large, which can slow down the performance of the workbook. It is generally recommended to use other methods, such as inserting images directly into the worksheet or linking to external image files, to avoid this issue."
@buddj83 I struggled with for hours as the MS help was useless. In my case the #BLOCKED! error was, *I think*, caused by the fact I was working offline. I managed to solve it by logging into the online version of Excel and trying the same =IMAGE() function and I got an option to allow images. Then when I went back to the desktop client I had the beige band @ZShark mentioned.
I just came across this problem myself. For my the issue was the image URL I was trying to pull from used http, rather than https. Using a quick SUBSTITUTE formula, I changed them all over the https and excel removed the block and my pictures pulled through.
This tutorial describes how to create AppStream 2.0 images that are based on Microsoft Windows Server operating systems. If you want to create custom images that are based on Amazon Linux 2 operating system, see Tutorial: Create a Custom Linux-Based AppStream 2.0 Image.
In this tutorial, you will learn how to create a custom Amazon AppStream 2.0 image that contains applications you can stream to your users, and default application and Windows settings to enable your users to get started with their applications quickly. To complete this tutorial, you must already have an image builder. If you don't have an image builder, see Launch an Image Builder to Install and Configure Streaming Applications.
To complete this step, you must log into the image builder with the local Administrator account or a domain account that has local administrator permissions. Do not rename or delete the local built-in Administrator account. If you rename or delete this account, the image builder will not start and image creation will fail.
If the image builder that you want to connect to is joined to an Active Directory domain and your organization requires smart card sign in, you must create a streaming URL and use the AppStream 2.0 client for the connection. For information about smart card sign in, see Smart Cards.
If an application requires the Windows operating system to restart, let it do so. Before the operating system restarts, you are disconnected from your image builder. After the restart is complete, connect to the image builder again, then finish installing the application.
In this step, create an AppStream 2.0 application catalog by specifying applications (.exe), batch scripts (.bat), and application shortcuts (.lnk) for your image. For each application that you plan to stream, you can specify the name, display name, executable file to launch, and icon to display. If you choose an application shortcut, these values are prepopulated for you.
The Display Name and Icon Path settings determine how your application name and icon appear in the application catalog. The catalog displays to users when they sign in to an AppStream 2.0 streaming session.
Repeat steps 2 and 3 for each application in Image Assistant and confirm that the applications appear on the Add Apps tab. When you're done, choose Next to continue using Image Assistant to create your image.
In this step, you create default application and Windows settings for your AppStream 2.0 users. Doing this enables your users to get started with applications quickly during their AppStream 2.0 streaming sessions, without the need to create or configure these settings themselves.
If your image builder is not joined to an Active Directory domain, on the Local User tab, choose Template User. This account enables you to create your default application and Windows settings.
If your image builder is joined to an Active Directory domain, in the Choose which user settings to copy list, choose the same account that you used to log into the image builder when you created the default application and Windows settings, then choose Save settings.
If your image builder is joined to an Active Directory domain, you require a domain account to test your applications, and the user already has settings on the image builder, you must reset the application settings for that user. To do so, select the user from the User to reset list, and choose Reset. When you're done, choose Switch user.
If your image builder is not joined to an Active Directory domain, choose Test User. This account enables you to test your applications by using the same policies and permissions as your users.
If your image builder is joined to an Active Directory domain, choose Directory User, specify the credentials for a domain account that does not have local administrator permissions, then choose Log in.
In this step, Image Assistant opens your applications one after another, identifies their launch dependencies, and performs optimizations to ensure that applications launch quickly. These are required steps that are performed on all applications in the list.
AppStream 2.0 automatically launches the first application in your list. When the application completely starts, provide any required input to perform the first run experience for the application. For example, a web browser may prompt you to import settings before it is completely up and running.
After you complete the first run experience and verify that the application performs as expected, choose Continue. If you added more than one application to your image, each application opens automatically. Repeat this step for each application as needed, leaving all applications running.
You can also add one or more tags to the image. To do so, choose Add Tag, and type the key and value for the tag. To add more tags, repeat this step. For more information, see Tagging Your Amazon AppStream 2.0 Resources. When you're done, choose Next.
If you choose a base image that is published by AWS on or after December 7, 2017, the option Always use the latest agent version appears, selected by default. We recommend that you leave this option selected so that streaming instances that are launched from the image always use the latest version of the agent. If you disable this option, you can't enable it again after you finish creating the image. For information about the latest release of the AppStream 2.0 agent, see AppStream 2.0 Agent Release Notes.
In 6. Review, verify the image details. To make changes, choose Previous to navigate to the appropriate Image Assistant tab, make your changes, and then proceed through the steps in Image Assistant as needed.
The remote session disconnects within a few moments. When the Lost Connectivity message appears, close the browser tab. While the image is created, the image builder status appears as Snapshotting. You cannot connect to the image builder until this process finishes.
After you create your image, you are responsible for maintaining updates for the Windows operating system. To do so, you can use managed AppStream 2.0 image updates. You are also responsible for maintaining updates for your applications and their dependencies. For more information, see Keep Your AppStream 2.0 Image Up-to-Date.
To add other applications, update existing applications, or change image settings, you must start and reconnect to the image builder that you used to create the image. Or, if you deleted that image builder, launch a new image builder that is based on your image. Then, make your changes and create a new image.
You can add one or more tags to an image during image creation or after you create an image. You can also copy the image within the same Region or to a new Region within the same Amazon Web Services account. Copying a source image results in an identical but distinct destination image. AWS does not copy any user-defined tags, however. Also, you can only copy custom images that you create, not the base images that are provided by AWS.
You can copy up to two images at the same time to a destination. If the destination to which you are copying an image is at the image limit, you receive an error. To copy the image in this case, you must first remove images from the destination. After the destination is below the image quota (also referred to as limit), initiate the image copy from the source Region. For more information, see Amazon AppStream 2.0 Service Quotas.
Copying an image across geographically diverse regions enables you to stream applications from multiple regions based on the same image. By streaming your applications in closer proximity to your users, you can improve your users' experience streaming applications with AppStream 2.0.
To check on the progress of the copy operation, return to the console and navigate to Images, Image Registry. Use the navigation bar to switch to the destination region (if applicable), and confirm that your new image appears in the list of images.
7fc3f7cf58