Is there an easy way to unpin Edge from the taskbar in windows 10 (1703)? Every time a user unpins and reboots it comes back. I have tried using the start.xml file with <CustomTaskbarLayoutCollection PinListPlacement="Replace"> but I cannot seem to get this working. Just wondering if anyone had a way to do it with AppSense 10.1 FR3.
Thanks
We have a Windows 2016 with Office 2016 Office setup with environment manager 10.1 (FR1). Our mail is in Office 365
when launching outlook 2016, we keep getting a prompt to enter username and password, although we have configured roaming of the credentials. From what I can tell, credentials are stored in
Contorl Panel > Credential Manager. There are two types:
MicrosoftOffice16_data: SSPI and MicrosoftOffice16_Data:ADAL
The first one has persistence set to Enterprise, which is correct. Data:ADAL entries have persistence set to Logon session.
It seems after logging off, the ADAL credentials are discarded (which makes sense from the persistence description).
After logging back in, we get prompted for Outlook credentials, and the Data:ADAL credentials are added again to the credential manager.
I found ADAL is related to Office Modern authentication, which can be disabled, but we don't want to do this.
any idea's?
many thanks
The boot.wim and boot_x64.wim that ship with LDMS include the Threshold I RTM version of WinPE. There have been two newer releases of WinPE since this version. The current most up to date version is RedStone I / 1607. New versions of WinPE are released every 6 months from Microsoft.
Some hardware such as the Surface Studios require this newer version in order to be PXE booted and provisioned.
Here are the steps to take to upgrade your boot files to a newer version of WinPE:
Step 1:
Download and install the latest version of the Windows ADK (or the version you need) from the below link to get Microsoft's release of the WinPE files that match the specific OS version:
Windows ADK downloads - Windows Hardware Dev Center
Step 2:
Run the Deployment and Imaging Tools Environment as administrator:
Step 3:
Download and run the following script from with-in the Deployment and Imaging Tools Environment CMD box that will prepare your WinPE files from Microsoft with the required modules for LDMS:
Create-WinPE.bat (attached to this document)
Step 4:
Take your prepared boot.wim and boot_x64.wim files from c:\winpe_x86 and c:\winpe_amd64 and copy them to this folder on your core:
Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot\clean\
*Note - backup the original files that are there incase you need to revert to the version that Ivanti ships with LDMS.
Step 5:
Backup your old production boot files. Create copies of the files located at Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot and put them some where safe (step 6 will overwrite them). However you must keep a copy of your old boot files here still. Do not simply move them to another location. Step 6 will be looking for these old boot files in order to migrate the HII drivers over to the new boot files, so if you rename them or move them instead of just making a copy of them - that step will not work completely.
Step 6:
On your core server launch an elevated command prompt and run:
This will upgrade your existing LDMS boot.wim and boot_x64.wim to now be RedStone I / 1607.
These updated files will be located at:
Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot
Additional notes:
- Bitlocker support is added via the Create-WinPE.bat script. (can use manage-bde.exe with-in WinPE)
- PowerShell usage without requiring full path is additionally added.
Is there an easy way to unpin Edge from the taskbar in windows 10 (1703)? Every time a user unpins and reboots it comes back. I have tried using the start.xml file with <CustomTaskbarLayoutCollection PinListPlacement="Replace"> but I cannot seem to get this working. Just wondering if anyone had a way to do it with AppSense 10.1 FR3.
Thanks
Hallo zusammen,
hat jemand schon Erfahrungen mit Windows 10 LTSB gesammelt?
Die Einführung von Windows 10 ist ja irgendwie unausweichlich. Aber nach der interessanten NWC-Roadshow kommen halt doch verschiedene Fragen auf bzw. wir machen uns Gedanken über verschiedene Szenarien.
Für den Standard-Office-Arbeitsplatz wird (da Volumenlizenzen vorhanden) ein "normales" Windows 10 Enterprise sicherlich zum Einsatz kommen. Mit dem Nachteil oder Effekt, dann man hier relativ häufig aktualisieren muss (Inplace-Upgrades). Sprich, bei einem normalen Lebenszyklus eines Rechners von 3 Jahren wird dieser min. ein, eher zwei oder gar drei Inplace-Upgrades bekommen. Länger lebende Rechner dementsprechend mehr.
Wenn ich jetzt überlege, wie lange das zu Hause mit dem Upgrade von Win 7 auf Win 10 gedauert hat, geht das in der Firma ja nicht mehr tagsüber, sprich das Upgrade muss nach Feierabend laufen. Allerdings gibt es bei uns auch genügend Rechner, die im 24/7-Betrieb laufen, hier müssen wird uns überlegen, was sinnvoller ist:
a) die LTSB-Variante nehmen und hoffen, dass die fehlenden Funktionien dort auch nicht gebraucht werden
b) regelmäßig die Rechner tauschen und durch aktuelle Installationen ersetzen. Sofern das mit der installierten Spezialsoftware und den Lizenzbedingungen verbeinbar ist...
Die LTSB-Variant hätte dann auch zur Folge, dass ein "anderes" Betriebssystem zum Einsatz kommt, sprich man hat zuerst mal ein Win 10 1709 Enterprise und dann ein Win 10 Enterprise LTSB. Später werden sich die Zahl der Installationsquellen erhöhen, wenn dann Win 10 1803 und 1809 hinzukommen, und irgendwann wird es auch Win 10 LTSB 2020 (oder ähnlich) geben...
Wie ist hier Eure Planung?
Gruß
Nils
Hi all,
I'm having some issues trying to deploy a batch file that will copy some powerpoint, excel, and word templates to their desktops. (We just had a rebranding)
On my test machines, the batch file runs fine for both Windows XP and Windows 7. I don't know what the problem is here as the batch files work fine without LANDesk, but when I go to distribute the task through LANDesk I get a "Package deployment failed" and a Return code 4.
Everyone has access to this share, I'm using a policy supported push, and I tried sifting through the log files with no real answer for why it isn't deploying.
I still haven't been able to find documentation on return code 4 as well.
Here's my scripting for both OS's:
Windows 7:
@ECHO ON
::Copies files to dekstop of current user *For Windows 7
xcopy "\\networkshare\tempstorage\Templates" "%systemdrive%\users\%username%\Desktop\Templates\" /O /X /E /H /K
Windows XP:
xcopy "\\networkshare\tempstorage\Templates" "%userprofile%\Desktop\Templates\" /O /X /E /H /K
Would appreciate any help in this matter!
Thanks.
Hello Community,
I have a few questions which you can hopefully answer easily. Googleing for an answer didnt give me any useful results.
I work at a company where Landesk is being used. Sometimes, for example when I need assistance from the IT Helpdesk they access my computer via Landesk remote access. I get a popup asking me if i want to allow access and when I click Yes thesy can use my computer remotly.
This is all ok, but I have the feeling that sometimes I am being accessed remotly whithout my allowance/interaction and someone is spying on me
I hope that doesnt sound to paranoid!
1) is it possible to access a computer with Landesk remote, while a local user is logged on and watch the screen without that user knowing it?
2) If yes, how can this be prevented by the user and how can the user notice when this remote spying happens? Can I monitor some ports or processes?
I have full local admin rights on my machine btw. and we run Win7.
Thanks for any useful answers.
We use version 2017.3
Each time user loges on it takes 30-40 seconds to establish a session. Then next time it takes about 2-3 seconds. But as soon as session time out limit of 20 mins is reached, first logon takes again 30-40 seconds.
We have 5 servers:4 for WebAccess, one as Application. System works using load balancer, sessions are created using InProc method.
Followed up all the performance configuration advises, sadly nothing helped.
Have anyone had the same issues? Any ideas what could be causing that?
Anyone having any luck provisioning machines with a Windows 10 1703 image? I built the image the same as I have for all of our other builds using the ISO from the Volume Licensing site, but I'm having trouble. Everything works properly in PE, but then after CTOS runs and the machine logs into Windows, I'm having a few different random issues:
Just wanted to see if anyone else had any experience with any of this. Everything works properly if we use our Windows 10 1607 image.
Thanks!
I'm well versed with user-CI linking in the Administration module in Console, via process or via data import but what about via WebDesk.
I want Analysts to be able to create a new CI via Webdesk form (OK doing this part already) and then manually link this CI to the user in Webdesk (hmm!). What's the equivalent in Webdesk of the "add CI to user" action in console administration; is there one?
All I can think of at the moment is to have a small change process with Add and Remove Actions which then run the link/unlink CI process actions as appproriate to the action selected and then close. However I'm certain the must be a simpler way that has escaped me so far in the documentation and this community. Maybe run a query and then it's a right click action on the results or something...
Can someone urgently advise?
Cheers
Julian
Hi
We have just downloaded the LANDESK 9.50 on a server. It is still running in trial mode. Im trying to test Distribution packages.
Im distributing a msi package. The destination has the new agent and it appears to be working fine. When I run the task it fails on a return code 105.
Here is an extract of what I see in the "view log file" option.
Processing package : Cisco VOIP Agent
Wed, 10 Apr 2013 10:14:23 File (\\-----\-----\------\-------\-------AgentDesktop.msi) is not in cache
Wed, 10 Apr 2013 10:14:23 Will attempt Peer Download.
Wed, 10 Apr 2013 10:14:23 Will attempt Preferred Server Download.
Wed, 10 Apr 2013 10:14:23 About to call DownloadFiles (1 files) with these settings:
Wed, 10 Apr 2013 10:14:23 m_allowedBandwidthWAN: 100
Wed, 10 Apr 2013 10:14:23 m_allowedBandwidthLAN: 100
Wed, 10 Apr 2013 10:14:23 m_maxDiscoveryThreads: 15
Wed, 10 Apr 2013 10:14:23 m_discardPeriodSeconds: 604800
Wed, 10 Apr 2013 10:14:23 m_preserveDirectoryStructure: 1
Wed, 10 Apr 2013 10:14:23 m_bUseWanBWForPush: 0
Wed, 10 Apr 2013 10:14:23 m_bSynchronize: 0
Wed, 10 Apr 2013 10:14:23 m_downloadControl: AttemptPeer
Wed, 10 Apr 2013 10:14:23 m_preferredServerControl: AttemptPreferredServer
Wed, 10 Apr 2013 10:14:45 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)
Where should I be looking to resolve this and any ideas what my problem might be?
Regards
Mike
Hello Community,
I have a few questions which you can hopefully answer easily. Googleing for an answer didnt give me any useful results.
I work at a company where Landesk is being used. Sometimes, for example when I need assistance from the IT Helpdesk they access my computer via Landesk remote access. I get a popup asking me if i want to allow access and when I click Yes thesy can use my computer remotly.
This is all ok, but I have the feeling that sometimes I am being accessed remotly whithout my allowance/interaction and someone is spying on me
I hope that doesnt sound to paranoid!
1) is it possible to access a computer with Landesk remote, while a local user is logged on and watch the screen without that user knowing it?
2) If yes, how can this be prevented by the user and how can the user notice when this remote spying happens? Can I monitor some ports or processes?
I have full local admin rights on my machine btw. and we run Win7.
Thanks for any useful answers.
Anyone having any luck provisioning machines with a Windows 10 1703 image? I built the image the same as I have for all of our other builds using the ISO from the Volume Licensing site, but I'm having trouble. Everything works properly in PE, but then after CTOS runs and the machine logs into Windows, I'm having a few different random issues:
Just wanted to see if anyone else had any experience with any of this. Everything works properly if we use our Windows 10 1607 image.
Thanks!
Hallo Community
Ich habe jetzt schon mehrere Einträge in diesem Forum gesehen bezüglich Upgrades der einzelnen Windows 10 Updates. Es gibt ja aus meiner Sicht mehrere Möglichkeiten welche möglich sind.
- WSUS
- DSM (In-Place Upgrade)
Welche Variante ist aus euerer Sicht die bessere? Wir haben aktuell die Version 1607 installiert und müssen jetzt wohl oder übel auf die neue Version 1709 Upgraden.
Ich bin euch sehr dankbar über Ratschläge.
Gruss Flavio
Hello,
Does anyone by chance have a template for the unattend file for Windows 10?
My OS provisioning template for Windows 10 works all the way up to the Configure Target OS section and then when it reboots, it comes up to setting up the machine for Windows 10. It never fully boots into my image. And if I do go thru the setup steps, after I login, ldprovisioning never seems to pick back up. Even after a reboot.
I have attached what I am using but it seems it never skips the OOBE section after the image deploys.
The boot.wim and boot_x64.wim that ship with LDMS include the Threshold I RTM version of WinPE. There have been two newer releases of WinPE since this version. The current most up to date version is RedStone I / 1607. New versions of WinPE are released every 6 months from Microsoft.
Some hardware such as the Surface Studios require this newer version in order to be PXE booted and provisioned.
Here are the steps to take to upgrade your boot files to a newer version of WinPE:
Step 1:
Download and install the latest version of the Windows ADK (or the version you need) from the below link to get Microsoft's release of the WinPE files that match the specific OS version:
Windows ADK downloads - Windows Hardware Dev Center
Step 2:
Run the Deployment and Imaging Tools Environment as administrator:
Step 3:
Download and run the following script from with-in the Deployment and Imaging Tools Environment CMD box that will prepare your WinPE files from Microsoft with the required modules for LDMS:
Create-WinPE.bat (attached to this document)
Step 4:
Take your prepared boot.wim and boot_x64.wim files from c:\winpe_x86 and c:\winpe_amd64 and copy them to this folder on your core:
Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot\clean\
*Note - backup the original files that are there incase you need to revert to the version that Ivanti ships with LDMS.
Step 5:
Backup your old production boot files. Create copies of the files located at Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot and put them some where safe (step 6 will overwrite them). However you must keep a copy of your old boot files here still. Do not simply move them to another location. Step 6 will be looking for these old boot files in order to migrate the HII drivers over to the new boot files, so if you rename them or move them instead of just making a copy of them - that step will not work completely.
Step 6:
On your core server launch an elevated command prompt and run:
This will upgrade your existing LDMS boot.wim and boot_x64.wim to now be RedStone I / 1607.
These updated files will be located at:
Letter:\Program Files\LANDesk\ManagementSuite\landesk\vboot
Additional notes:
- Bitlocker support is added via the Create-WinPE.bat script. (can use manage-bde.exe with-in WinPE)
- PowerShell usage without requiring full path is additionally added.
Users are not logging off after the EM Agent has been upgraded to 10.1 FR4 HF2, there error seen is:
Application popup: winlogon.exe - System Error : The program can't start because Axe2.dll is missing from your computer. Try reinstalling the program to fix this problem.
I have removed and reinstalled the agent but no change
Has anyone seen this before
Regards
Garry