Aarbron

Thanks atcoates. From what I can tell, Scansnap installs in "C:\Program Files (x86)\PFU\ScanSnap" and Scansnap Manager accesses the executable in subfolder Driver > PfuSsMon.exe. I've given staff full permissions to the folder but it didn't seem to resolve the problem. I'll double check the security settings. I'll also have a look at the permissions tool from the above link. Thank you

Hi all, I've encountered a frustrating issue with Fujitsu S1500 desktop scanners and the Scansnap software. It's not running for users (unless they're given admin privs to the workstation). The little blue S icon in the systray has a red cross through it. If a user presses the blue button on the scanner, it just flashes but the device doesn't do anything. The devices are connected via USB. The computers are all Windows 10 64bit - a mixture of RM Windows 10 Education version 20H2 and 21H2. The network is CC4 Connect OnPrem (2016 R2 DCs). It's got to be a permissions issue but I don't really know what to look for. Has anyone else had this problem? Regards Jonathan

Thank guys, I'll do some further testing next week.

Hi Cazab, Yes, we do. Regards

Hi all, Apologies if this has been posted in the wrong place. Has anyone had any experience with Displaynote Broadcast? We're trying to get it working with our staff/student accounts (Windows 10 64bit machines) but it looks like its being blocked when we attempt to broadcast/share the desktop. We've followed this guide and unblocked everything in the Smoothwall firewall, even the IP ranges: https://support.displaynote.com/hc/en-us/articles/4417461786769-Network-requirments The end user recieves the following error: Bypassing the firewall works. We must be missing something but not sure what, does anyone have any suggestions? I contacted Displaynote Support and they just advised that all IPs in the range list are whitelisted. I feel a bit uneasy letting multiple ranges through the firewall! Regards Jonathan

Thanks mate. I'll give it a try!

Hi, Do you mean the build disk? I haven't regenerated it for sometime, but the build disk always worked until recently. I can try regenerating the WinPE5.0 disk again.

Hi It's happening to any machine we attempt to rebuild - Lenovo ThinkCentre M71z AIOs, Dell 3040, 3050s etc. Never had a problem in the past with said machines. We had a bit of a 'tidy up' in the RMMC. I'm beginning to wonder if a package has been deleted that was part of the build process. We only deleted some old Windows 7 KB packages from what I can remember and no new packages have been introduced to the RMMC since the build failures have occurred.

Hi, We've already contacted RM. It's been escalated to third line but it looks like they're stumped... Regards Jonathan

Hi all, We have a CC4 Connect OnPrem network (Server 2016 + Windows 10 64bit 1909 clients), single site. Never had a problem when it came to re-imaging PCs until recently. The builds kick off fine using PXE but when they get to the CC4 Bootstapper Updating Installation Agent phase it errors at 'Error unable to add computer to network'. When we check RMMC/DNS and AD - the hostname for the machine is there but the machine appears 'offline' with no other information (serial number, OS version etc). Looking at the error in more detail it says something about error updating Computer Manaager RM.Networks.Comms.RemotingFramework.RemotingExeception: Exception caught in CheckComputerAdded RM.Networks.ComputerManager.Core.ComputerManagerException. I've added the errors as attachements. We've tried removing the computers from RMMC and DNS and rebuilding. We've fully patched the two 2016 DCs etc, clearly RM Host Service cache on both servers etc....out of ideas. Any help guys would be great.

Hi all, I'm not at all experienced with rolling out Adobe's update packages (.msp). Does anyone know if a MSP file can be imported into CC4/RMMC and assigned to clients via the usual package.ini import? If so, what is the correct way to do this? I can import msi and exe packages into the RMMC, but I've never tried doing it with an msp package. The package in question is AcrobatDCUpd2100720091.msp https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuoussept2021.html#dccontinuoussepttwentytwentyone Thanks all.

We've just encountered the black screen login issue (for students, not staff) on our CC4 Connect OnPrem (2016 + Windows 10 202H) network. I've just tried the suggestion to disable the Adobe updater service, since we have Adobe CC 2019 on all of our workstations. Now I just need to find a problematic machine to see if it resolves...

Hi Boot3988 Unfortunately, that didn't work. We rebuilt a number of computers which weren't working (fingers crossed) they're working again. Having said that, we've just had a call to say one of the rebuilt PCs is now black screening when a student logs in! I might have to contact RM because I'm out of ideas. regards Jonathan

Hi hallb15, Unfortunately, this didn't work. Weirdly, our test.student account logs in fine on some machines but not on others. If the black screen issue occurs for one student user, it then seems to affect all student users who log onto said machine. Regards Jonathan

Hi all, I've encountered a very frustrating issue with student logins on our CC4 Connect OnPrem (Server 2016) network. All clients are Windows 10 64bit 202H (October 2020) CC4 builds. We seem to suddenly have an issue where a student logs in and it just sits at a black screen during the login process. It doesn't happen for staff. Staff and students use UEV profiles. I've had a look on RMs knowledge base but there doesn't seem to be much in relation to this issue. I've tried the following: 1. Side by side comparison of two workstations, both same make and model with the same Windows Updates applied - one will work the other won't 2. Fully updating one of the affected machines - Windows and driver updates. No luck 3. Restarting the RM Host service on the affected workstation. No luck 4. Bouncing the domain controllers. No luck 5. Recreating a test student account. No luck Rebuilding a computer by fully removing it from the RMMC seems to work. However, this solution is unfeasible since we have 500+ workstations on the network. Has anyone come across this frustrating issue before? I'm leaning towards some funky permissions issue, since it works with a staff account. Thanks all.