Techyboy19

I have seen this issue before but mine occurs after bulk importing users via CSV. It runs the import but fails to add any users. I then get told all the card numbers are in use and you cannot add manually either then. When this happened to me a few years ago I had to export all users and match all users tokens to their unique user ID and import again after wiping all the users. I feel like it’s a user ID issue personally. Since then I’ve not used the bulk importing tool. Don’t know if you get this issue too but if I try to add a new operator to Net2 it adds it and sets the password, shows in the operator list but never appears in the drop down to login. Hopefully they can offer you some advice to fix this issue.

Slightly different answer to the question but are you just wanting a list of the devices so you can go around and remove the user that was left behind. If so could a startup .bat script be an option to simply delete the user assuming you have another local admin account in that Machine. For example the script below deletes the specified local user and creates a flag file once completed. This could just run on all pcs as long as that local username isn’t needed anywhere for anything on any of them devices. @echo off set FLAG=C:\ImageDeployAccountRemove.flag REM Check if we've already run if exist "%FLAG%" ( echo ImageDeployAccountRemove already processed. Exiting. exit /b 0 ) REM Delete the local user account net user test /delete REM Create the flag file to prevent reruns echo done > "%FLAG%" exit /b 0 On line net user test /delete you would replace test with the username in question. I would then remove the policy once I’m happy that the account has left all the PCs it needs to

I have some instructions a colleague left me when he left and I’ve never had any issues. Install RDWorks whilst logged on as an administrator Press Install The installer will unpack Press "Install" at the bottom Wait for the install to finish Create a folder called "temp" (CASE SENSITIVE) within the RD works folder(C:\RDWorksV8) If you don't do this, it will throw errors when opened and every time the working space is edited in any way. Head to the install location (C:\RDWorksV8) and give users "MODIFY" permissions. Check that the software can open with a non admin account.

I had a similar issue with newer version hanging once installed and MDT therefore getting stuck. I installed the older version and hoped it would auto update. It installed but seems the update did not work and when a user logged into drive it told them they needed to upgrade. I have being using the below script to install. Create DriveInstall.bat and place it in the MDT Google Drive application folder and then in the Drive Install command on MDT point to DriveInstall.bat. @echo off REM Silent install of Google Drive for Desktop for MDT REM No desktop or G Suite shortcuts SET INSTALLER=GoogleDriveSetup.exe IF EXIST "%~dp0%INSTALLER%" ( echo Installing Google Drive silently... "%~dp0%INSTALLER%" --silent --desktop_shortcut=false --gsuite_shortcuts=false REM Write date and time to C:\DriveInstalled.txt echo Google Drive installed on %DATE% at %TIME% > C:\DriveInstalled.txt EXIT /B 0 ) ELSE ( echo ERROR: %INSTALLER% not found in script directory. EXIT /B 1 )

Think I finally managed to solve this one, fingers crossed. It seems to be related to the GPO that disables the first sign in animation for new users of the machine. I have the first sign in animation enabled now for new users and the start menu worked for me again as it should. Thinking it’s logs in too quickly with this disabled and does not allow the needed start menu related packages to initiate or start up. You see the desktop appear then seconds later the taskbar, this was not the case for me when the first sign in animation was disabled, both are already there once preparing windows finishes.

Update on this, it only seems to affect domain users and has only become an issue in the last few months. I am thinking that a windows update could have caused this issue as on an unpatched PC in from January I cannot replicate the issue but once patched the issue occurs. Thanks

Thank you for the response Have you done any debloating of windows or anything like that and has it happened since day one? 24H2 I am guessing? Thanks

Hi, I am working on my next years Windows 11 Image and appear to have an odd issue where the start menu search does not work on the first login. The Start menu opens and the search appear but when you type nothing appears. In task manage the search is suspended after a log out and back in all is good and works but each time you use a machine where you don't have a local profile the issue occurs. Has anyone else experienced similar ? Thanks

Hi all Has anyone ever had an issue with Microsoft Publisher 2019 where a user cannot open the publisher files they download on their laptops. Publisher opens however it then changes to not responding and will either crash or take upto 10 mins to open. This only seems to happen on the users laptops and only when they are connected to the network, if they access the file via of the offline files cache they can open it. Thanks

This may work, howver this is not an error I have personally experienced. Get-AppxPackage Microsoft.Copilot_0.4.2.0_neutral__8wekyb3d8bbwe | Remove-AppxPackage Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -eq "Microsoft.Copilot_0.4.2.0_neutral__8wekyb3d8bbwe"} | Remove-AppxProvisionedPackage -Online

I think you will need to remove this package for the same reasons as above. Please try the following: Remove-AppxPackage -Package Microsoft.LanguageExperiencePacken-GB_26100.24.38.0_neutral__8wekyb3d8bbwe Remove-AppxProvisionedPackage -Online -PackageName Microsoft.LanguageExperiencePacken-GB_26100.24.38.0_neutral__8wekyb3d8bbwe Hopefully this will help.

No problem, I can’t remember exactly but if your computer has multiple users on it you may need to use the All Users argument instead. Get-AppxPackage -AllUsers -Name "MicrosoftWindows.Speech.en-GB*" | Remove-AppxPackage This should then uninstall and allow sysprep.

Think it is something to do with the Microsoft speech package being installed for the administrator user but not all users. I fixed a similar issue by running the following as admin in powershell. Get-AppxPackage -Name "MicrosoftWindows.Speech.en-GB*" | Remove-AppxPackage This will remove the package and should let you carry on.