Hi Julian
How lovely to hear from you. Yes it is on Webdesk that I am having the problem One of the analysts filtered a column on one of his gadgets and then deleted the column, I just wanted to his dashboard and not everyones. I have given him admin access but he still does not seem to be able to see his original dashboard as he has made quite a mess. Any suggestions would be useful.
Hi Elaine
He will have created a personalised version of his dashboard and unfortunately the only way to remove it is via a SQL script.
This article explains how to do. A change made to a dashboard isn't reflected for some or all users in Web Access (Web Desk or Self Service)
Regards
Julian
in dem updatemanager sollte irgendwo oberhalb der roten zeile stehen welche voraussetzung nicht erfüllt ist
(im logfile steht's natürlich auch - ebenfalls weiter oben)
I think you need to be a bit more specific about what doesn't work here after Motaz suggestion.
IMHO the created date/by fields are a bit superfluos on a “ghost” window unless you plan to reference them later. As you’ve found already, the advantage of a “ghost” window is presenting imformation captured on the main screen but it is also an “Achilles Heal” when it comes to persistence type attributes such as create date and useras these will also be the values of the main Change lifecycle object
It also depends on your process and whether you can loop back and hit this action more than once because you’ll then be overwriting your data on each pass.
IMHO you should create a “Review” collection business object and follow your “ghost” window manual action with an automatic action that copies the ghost window fields onto the collection via valuetypes or calculations so you snapshot on every pass. The collection itself then has its own persistence types for create date, create user etc that you can see when you later review.
Julian
MarXtar Ltd
Create a before save calculated field with dependency of the colour attribute and convert it to html colour code string and then you can query on it if you want. You will need to back fill them though via schedule manager one-off job.
Julian
MarXtar Ltd
Ah ok da werd ich das nächste mal aufpassen. Das heißt wenn ich z.B. ein Package einer Gruppe in der mein Client Mitglied ist zugewiesen habe und dann eine Revision anlege und "jetzt lokal installieren" sage er mir immer das Package von der Policy installiert? Und wie ist das mit dem Installationsverzeichnis, er nimmt hier immer das Work Verzeichnis oder?
Sprich Distribution vorbereiten + Lokal installieren = Work
Anschließend Distributieren und Policy = Install Verzeichnis?
Hi Mel,
habe es mal gestested und der Client führt einen Reboot durch. Das Paket steht dann noch auf pending, doch nach dem nächten PXE Verbindung zum BLS wird das Paket auf compliant gesetzt. Es wird daher mein Pre OS Action Package nicht erneut angezogen.
Anmerkung allgemein:
Finde es schade, dass in Windows PE keine DSM Befehls Interpretation gibt.
Thanks for the input. I agree this can increase administrative overhead for managing those network locations, but there would be for either the Application Control config or the network locations. I think the key to successful whitelisting isn't necessarily technology, but processes.
Getting these apps moved to a single location isn't feasible for most enterprises with a history of legacy applications and any real lack of application management. With Trusted Owner is use, it wouldn't matter if users had read/write access to the network share - as long as they don't have Full Control they can't change owner, so overwriting or adding new exe's wouldn't allow those executables to run.
Hello Frenk,
we came across your support case.
VelocityCE got only network traffic log and coming into details of your webpage not working this can be an issue with the configuration settings on velocityCE.
Especially please check these three settings under configuration settings and make sure you enter correct details under Velocity server 1.
As we received your webpage from the support case, we changed these options inside configuration settings to make it work on VelocityCE
1. Enable WEB Alternate Browser support
2. Make sure WEB Engine type is on "Enhanced" otherwise VelocityCE will use pocket internet explorer instead of VelocityCE webkit
3. Check WEB User Agent you can change it to according to the Windows OS version
Once settings are done save it and click on "Config only" in order to send the configuration to the device.
Good Morning -
Does anyone have any ideas of how long this would run for?
Everything is configured on the config:
I think our database Data (ROWS type_desc) is ~ 4.6GB if it has any impact.
This has been 'running' since 1pm yesterday.
Hi Mark,
When I go into Device Manager it appears that Windows cannot see the USB before I unplug and reinsert it.
If i reboot before doing that it does then pick it up when going back into Windows 10, so it looks to be on the initial reboot it fails to find it.
I gather it is USB 3.0 though I can't try another port as it is the only one it has.
Cheers
Phil
When I set mine up for department I based mine on the Location configuration so the relationship uses the FusionLink table and zero to many
I have tested the permissions and appears to work correctly with this relationship configuration:
When Edit is ticked my user can edit, when unticked the edit button is removed.
Check your appserver log and configdb log that seems like a longtime to be running. Did you rebuild your metadata index before running?
This took 2 minutes to completely run through my demo database which is about 2.5 GB in size
Funny you mention that, AlasdairRobertson - I noticed yesterday that I never tried a similar setup to Location.
Thanks for your time on this, will give it a try and let you know how I get on
What version of ISM are you running it is working on my demo tenant after enabling full text searching on the My Item > Incident relationship
Well it is food for thought.
If I could I would just start from a nice fresh install and start again but I think we have too much in the system now.
We use it quite a lot now for patching and deployment etc. so it is probably best to just carry on as we are.
Sometimes I just like to have a nice clean start with things.
Indeed and yes I am aware I can lock it down to specific devices.
However to me that defeats the purpose of the self electing process and means if that one device fails we are back to square one.
So we will probably stick with the single PXE server scenario and keep the admin on the security tool to a minimum.
Hallo Klaus,
danke für deine Antwort, aber ich habe es auf einem anderen Weg hinbekommen. Ich schieße die Proxy-Konfig per Regkey mittels escipt rein...hatte für den Regkey das falsche Format! Kaum macht man es richtig, schon geht's!
Gruß
Thorsten
Hi Team
Wondering if anyone has a simple troubleshooting guide for the agent comms.
It used to talk to my demo VM, but now that has stopped.
It is still sending log info up but will not apply a new policy.
Any first steps direction would be awesome :-)
Thanks
Shane