User Profile
James_Randall_1978
Brass Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: Account Used To Logon needs to be different from Logged in Windows User - Help Please
Hello, no sadly it's still an issue, I also now have issues where our Office 365 has migrated to another tenant and our Azure AD used with WVD is in our original tenant. Which over time is causing the Remote Desktop application to fail MFA and mean I'm having to move users back to a traditional RDP RemoteApp deployment. Which is very annoying.6.6KViews0likes0CommentsRe: RemoteApp user locked out of PC
James Bliss We've also just started to experience this as well. No idea how to resolve it without the session log off you've described. It's almost as though the user is being reconnected to the same session host and session, but the session is not being unlocked upon that reconnect.4.7KViews0likes1CommentRe: Account Used To Logon needs to be different from Logged in Windows User - Help Please
Soo Kuan Teo , Hello, Assuming version 1.2.1446.0 is the release version to fix the bug I described, then I'm afaid it is still nto fixed, at least not for myself. I'm not certain if perhaps I'm doing something wrong but the client stil logs in as the Windows 10 user, not the account the resources are being pulled from.8.2KViews0likes2CommentsRe: Scanner Redireation
Scott1963 , I think you need to ensure some group policy (local or domain based, I used lcoal for testing first) have been applied. I found the below link useful. This got me far enough that my Kodak desktop scanners showed up in the printers and devices within the WVd session. However they still did not work, I think the issue is the large amount of data being transfered when scanning. Unlike a printer or control device you're talking a lot of data over the RDP session. https://tighetec.co.uk/2020/06/09/usb-redirection-for-wvd/ Failing that perhaps try using a USB Server device like the second link, which allows you to share usb devices across a network with compression. https://www.silextechnology.com/connectivity-solutions/device-connectivity/ds-51023KViews0likes3CommentsRe: Account Used To Logon needs to be different from Logged in Windows User - Help Please
Hello, Sorry to be a pain, but do you have any ETA on when this might be resolved? I have around 60 users in my company I cannot migrate to WVD RemoteApps at the moment. A reough idea on ETA would be very helpful to allow me to plan. Thank you.8.2KViews0likes4CommentsRe: WVD session shadowing
Christian_Montoya , Hello, Could you perhaps please explain in some greater detail how I would be able to do what you have described? We currently only have one Windows 10 WVD host, so identyfying the host concerned is not an issue, I am unsure how to use "the shadowing RDP capability" or where to access this?8KViews0likes2CommentsRe: Account Used To Logon needs to be different from Logged in Windows User - Help Please
Soo Kuan Teo Hello, thank you for trying to understand better my situation. Thre are only two accounts to be clear. Windows 10 dekstop PC login - Account A Windows Virtual Desktop User - Account B 1- User A logs into domain joined PC. 2- User A opens Remote Desktop Client (WVD edition) 3- User A uses Account B credentials to subscribe to WVD 4- The resources for Account B show up in the Remote Desktop Client app. 5 - User A double clicks one of the RemoteApp programs (resources) 6- The RemoteDesktop connection begins, however the user is logged in using Account A, not Account B. The RemoteApp fails to open as Account A is not authorised for RemoteDesktop login on the server. The issue being when account B is used to subscribe, it should also be used for the connection. Otherwise it could become very confusing.8.3KViews0likes10CommentsRe: Account Used To Logon needs to be different from Logged in Windows User - Help Please
Soo Kuan Teo Hello, Thank you for your response, while I can use the new version of the RDP client to add resources that are tied to a different email/account from the main Windows account, when a connection to those resources is established I find the main Windows account user is used for that connection. Ideally the specified email.account being used to find the resource feed should then also follow through and be utilised for the connection, particulalry as at that point 2FA has already been used to verify the user to generate the resources available. So to sum up, the account used to login to the workspace is not the account used to login to the server. When one would think it really should be, I'll admit it's an unusual case, but an important one none the less as currently it could be considered misleading. I did try the MS Store Remote Desktop app, this refuses to display any resources and as such I cannot proceed any further with it. The WVD Remote Desktop client does seem to be the way to go, I was hopeful when the new update was released that it would perform as I need it to, sadly not quite.8.3KViews0likes12CommentsRe: Account Used To Logon needs to be different from Logged in Windows User - Help Please
Soo Kuan Teo, Hello thank you for your response. I am having difficulty in establishing what the RemoteApp server address is for the WVD RemoteApp resources? I've tried inputting the one from the WVD Client however it doesn't seem to work.8.5KViews0likes14CommentsAccount Used To Logon needs to be different from Logged in Windows User - Help Please
Hello, I am able to successfully deploy WVD for all of my users who login to Windows 10 dekstpos as a named user. My RemoteApps load fine and all is well. The issue comes where we have a number of depot locations where for exmaple they might have 2 or more PCs which all login to Windows 10 as the same domain user (primarily for simplicity, they do not need seperate email addresses and need access to the same OF365 mailbox). So in these locations in our previous non WVD deployment I would have two or more domain users (dep01-2, dep01-2) which would login and run our RemoteApps. However when I assign these users to the ApplicationGroups the WVD client refreshes and shows the correct apps, when syncing as the dep01-1 etc accounts. However when the connection is initiated the REmoteDekstp client is choosing to use the logged in Windows account (which is the same on both PCs) instead of the defined RemoteApp domain users. I hope this makes sense, I'm happy to explain further. In short I need to be able to specify a WVD RemoteApp user that is different from the OF365 and Windows 10 logged in user.9.1KViews0likes17CommentsRename WVD Workspace
Hello, I'm using the new Spring 2020 method for deploying RemoteApps etc. While following the setup documentation guide I wasn't aware that what I called my workspace effectively becvomes the title for the group within the WVD client program as well as presumably the folderon the start menu. Is there any facility to rename a workspace (I currently have it named somethingless obvious to the end user) without having to create a new workspace and add in all the published remoteapps again?Solved9.1KViews0likes4CommentsRe: FSLogix profile configurations for App virtualization only scenario
bhushangawale, I may be mistaken in this, however it's preferable to have the UPD/FSLogix containers stored in a central location, as opposed to locally on each host's C drive. If you're deploying RemoteApps via WVD then I can see no reason not to take advantage of the benefits of the more streamlined FXLogix containers instead of the more usual UPD storage on a network accessible drive. Also I'm not aware of how to configure that location under the WVD way of doing things. Likely FSLogix is your only real method of configuring where they will reside. It's also Microsoft best practice at this point for WVD deployments, even if the user profiles are goign to be small due to only being RemoteApp deployments.4.3KViews0likes1CommentRe: Gallery Image vs Blob Custom Image
cjitsolutions Hi, I've limited experience, but I'll try and answer as many of your points as possible: 1. Primarily the usage of a custom image is to aid in the configuration process. As you say programs, registry tweaks, user language/input options, required files and nay other tweaks can be performed upon one VM. Then it's shut down and a "Gold" image is created. You can then use this to create/spawn your pool of Vms from as a base image. It's particualry useful if you have a large WVD pool with many hosts. As one might imagine once you get over 5 or more VMs perfomring the required setup "Tweaks" can take a long time, with the possiblity of missing something along the way. 2. Any hosts built from a custom image are ONLY built from that image. So their OS disk is formed of a COPY of the custom image. No changes are made to the image in any way. 3. As stated before, the custom image is not 2logged into", it's better to think of it as the image used as a copy for each VMs OS disk. If you need to update a custom iamge you would need to create a Vm using it as the image, then make your required changes, then create a new image from that VM to replace the older one. 4. The Microsoft gallery image is maintained by Microsoft, so in that sense is pure. As for whether Microsoft keep it up to date, I'm unsure. A quick Google produced no relevant results. So I'll have to leave that to someone else to answer. One would hope the gallery images are kept somehwat up to date. I do know I've still had Windows updates to install when using a Microsoft Gallery image, so how up to date they are is debateable.. Hope this helps somewhat.1.9KViews1like0Comments
Recent Blog Articles
No content to show