Windows 7 Event Log for Desktop Background Change
We had an issue with our company where someone changed the desktop background on a shared machine to something inappropriate. We're trying to find out if Windows performs logging of when the desktop background is changed so we can track down how it happened. I've tried doing a Google search and combed through the event logs on the machine, but I can't find any info.
I'm a coder and not a sysadmin, so I'm not very familiar with this kind of thing.
Thanks for the help!
windows-7 logging desktop-customization
add a comment |
We had an issue with our company where someone changed the desktop background on a shared machine to something inappropriate. We're trying to find out if Windows performs logging of when the desktop background is changed so we can track down how it happened. I've tried doing a Google search and combed through the event logs on the machine, but I can't find any info.
I'm a coder and not a sysadmin, so I'm not very familiar with this kind of thing.
Thanks for the help!
windows-7 logging desktop-customization
add a comment |
We had an issue with our company where someone changed the desktop background on a shared machine to something inappropriate. We're trying to find out if Windows performs logging of when the desktop background is changed so we can track down how it happened. I've tried doing a Google search and combed through the event logs on the machine, but I can't find any info.
I'm a coder and not a sysadmin, so I'm not very familiar with this kind of thing.
Thanks for the help!
windows-7 logging desktop-customization
We had an issue with our company where someone changed the desktop background on a shared machine to something inappropriate. We're trying to find out if Windows performs logging of when the desktop background is changed so we can track down how it happened. I've tried doing a Google search and combed through the event logs on the machine, but I can't find any info.
I'm a coder and not a sysadmin, so I'm not very familiar with this kind of thing.
Thanks for the help!
windows-7 logging desktop-customization
windows-7 logging desktop-customization
edited Apr 9 '17 at 8:07
fixer1234
19k144982
19k144982
asked Jun 27 '13 at 0:37
RobotNerdRobotNerd
11113
11113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Use Process Monitor v3.05 and set filter registry key HKEY_CURRENT_USERControl PanelDesktop
Or set WallPaper
value and set read only permission at key HKEY_CURRENT_USERControl PanelDesktop
.
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f612562%2fwindows-7-event-log-for-desktop-background-change%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Use Process Monitor v3.05 and set filter registry key HKEY_CURRENT_USERControl PanelDesktop
Or set WallPaper
value and set read only permission at key HKEY_CURRENT_USERControl PanelDesktop
.
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
add a comment |
Use Process Monitor v3.05 and set filter registry key HKEY_CURRENT_USERControl PanelDesktop
Or set WallPaper
value and set read only permission at key HKEY_CURRENT_USERControl PanelDesktop
.
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
add a comment |
Use Process Monitor v3.05 and set filter registry key HKEY_CURRENT_USERControl PanelDesktop
Or set WallPaper
value and set read only permission at key HKEY_CURRENT_USERControl PanelDesktop
.
Use Process Monitor v3.05 and set filter registry key HKEY_CURRENT_USERControl PanelDesktop
Or set WallPaper
value and set read only permission at key HKEY_CURRENT_USERControl PanelDesktop
.
answered Jun 27 '13 at 0:59
STTRSTTR
5,86711317
5,86711317
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
add a comment |
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
This looks like it will disable a user's ability to change the desktop background. Good for future use, but not what I need now. We're trying to perform a system audit to find out the date/time of an existing background change event, and ideally the user who made that change.
– RobotNerd
Jun 27 '13 at 17:06
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
@RobotNerd To do this, set up audit of the registry. If this happens for all users, then you have either security flaws, or the attacker has details of the system administrator. Or as an administrator ran some files to work with malicious content. For example correcting the problem user under self account. In general, spend time on other things. And security scenarios.
– STTR
Jun 27 '13 at 21:45
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f612562%2fwindows-7-event-log-for-desktop-background-change%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown