User Profile
ProjectVRD
Brass Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Edge for Business 64-bit MSI's not installing 64-bit Edge
We are trying to install the 64-bit of Edge via the Edge for Business MSI, however after executing this MSI the About info for Edge still says 32-bit. We look into the registry and the Uninstall section for Edge is in the 32-bit section of the hive. This has been an issue for a very long time and we did see it was reported a last year but nothing has been done about it. How do I contact the developers to ask that this is urgently fixed? The 32-bit installer should only install the 32-bit version and the reg keys put into the correct places, and the 64-bit should only ever install the 64-bit version and the reg keys put into the correct places. As it stands Edge is not a viable option for central control because the detection in Azure Endpoint Manager really does need to know if they software is in the right place (64-bit\32-bit etc). These are all Microsoft applications and services so the impact is on businesses and with the upcoming end of IE11 we need Microsoft to ensure that Edge is ready for business use... it is not with this problem. Edit: This issue manifests when changing between the 32-bit and 64-bit versions of the software which is more common than some would believe due to 3rd parties (such as Barclays bank) only creating services that will work with one particular kind of application install (32-bit Edge or 64-bit Edge for example). Edit2: Please also note that the 64-bit MSI always installs the software in 'Program Files x86', this must be changed to install in the 'Program Files' folder on 64-bit operating systems. Essentially this software is not ready for Production in businesses.1.2KViews0likes0CommentsWe need an option to hide Inactive devices from TVM statistics
There is no option to hide 'Inactive' devices from skewing the TVM statistics. This makes tackling and reporting on existing threats and vulnerabilities unnecessarily difficult, a device that has been rebuilt can show in excess of 900 vulnerabilities but in reality that device no longer exists. The situation across the estate would (in our enterprise anyway) actually be around 40 vulnerabilities which is an incredibly large difference. When reports across the industry are required on 7 day and monthly cadences management are always wondering why their IT teams are not able to do their job and get machines secure, of course the machines are secure but Defender 365 just will not allow us to show that. If an option to exclude 'Inactive' devices can be added this would be of massive benefit to all organisations that use the TVM feature, it means nobody would be hunting down rememdiation and including reports for devices either no longer exist or haven't reported in to Azure for an extended period of time.1.4KViews2likes2CommentsRe: Dev channel update to 79.0.301.2 is live
Nice stuff josh_bodner I would like to make a suggestion, can you carry over the Site To Zones GPO feature that exists for Internet Explorer? It's a god send in Small to Medium sized businesses that with Internet Explorer we can fully stop users downloading files from websites unless we assign the website one of the number values in the Group Policy setting to be either "1 - Intranet" or "2 - Trusted Sites". This ofcourse implies that the GPO setting to prevent users downloading is also carried over20KViews2likes0CommentsRe: Top feedback summary for September 24
David Rubino I don't think that under any circumstances you should allow google account sign in for Microsoft Edge. This could potentially result in Google interfering with Edge development in the future, it is much harder to appease the users if you need to remove the feature at a later date when Google unfairly changes its T and C's. This is of course just my opinion but it feels like it would open a can of worms as Google is a competitor, and quite an aggressive one at that. Google has a long track record of breaking the functionality of their services in other companies web browsers, so when they do this with google account sign in on Edge it will be Microsoft who will get the blame from Edge users who were using Google sign in. It's a risk assessment issue before a functionality assessment issue and these risk issues are easily avoided by not giving Google the opportunity to play hard ball in the first place.4.5KViews4likes3CommentsRe: Three known bugs in the latest build of Win10 version 1903
HotCakeX I'll be honest, I haven't yet seen the RDS black screen issue and I had to do alot of it today on the latest build. I haven't had the opportunity to test against the other two issues. What I can say though is that our domain connected computers are still having the Search not responding problem, our pilot scope if 54 computers and all 54 of them have this issue. Starting with the Sept 10th update, it also rendered right click context menu on app icons (on taskbar) and Action Center completely inoperable. This continued with the out of band IE11 patch. But the update from last a couple of days brought back the app icon context menu's and Action Center at the second time of Microsoft trying, the search feature is still completely inoperable though. This may or may not be important, but the affected computers were all built via WDS as 1709 systems and they had several provisioned apps removed including Xbox which funnily enough break Photos (because a .Net Runtime that Photos in 1709 relies upon is also removed, an unfortunate way that Microsoft set their apps and dependencies up). Funnily enough the way Photos was broken in 1709 shows symptons identical to the way Search is broken in 1903, no error message or anything seemingly detrimental on screen except that it plainly doesn't launch. Now after updating these 1709 builds via WSUS to 1903 the new Photos app worked (hoorah, some users were happy) but I don't think they will appreciate losing Search since Sept 10th so all cumulative updates are on hiatus. Something important to note, all 1903 builds deployed from WDS and using the same method to remove provisioned apps are not affected by the Search problem using the three cumulative updates since Sept 10th.5.3KViews0likes0Comments
Recent Blog Articles
No content to show