TechSupport247
My feedback
-
56 votes
TechSupport247 supported this idea ·
-
3 votes
TechSupport247 supported this idea ·
-
33 votes
TechSupport247 supported this idea ·
-
6 votes
TechSupport247 supported this idea ·
-
10 votes
TechSupport247 supported this idea ·
-
3 votes
TechSupport247 supported this idea ·
-
25 votes
TechSupport247 supported this idea ·
-
23 votes
TechSupport247 supported this idea ·
-
8 votes
TechSupport247 commented
"3. Malicious person has admin access to the server, but not Domain Admin rights, modifies script"
The problem is having an unauthorized person having administrator access to the server.
-
6 votes1 comment · General Feedback » Interoperability & Integration · Flag idea as inappropriate… · Admin →
TechSupport247 supported this idea ·
-
102 votes
TechSupport247 supported this idea ·
-
12 votes
TechSupport247 commented
This is one of several task scheduler bugs introduced in 1607. I can't believe these bugs haven't been fixed yet (no change in 1703).
Other bugs include:
- repeating tasks only start when the starting date is set in the future
- updating Shadow Copy schedules does not update the associated scheduled tasks
- scheduled tasks with multiple actions only execute the first action, unless "run only when user is logged on" is selectedTechSupport247 supported this idea ·
-
7 votes
TechSupport247 supported this idea ·
-
11 votes
TechSupport247 supported this idea ·
-
10 votes
TechSupport247 supported this idea ·
-
21 votes
TechSupport247 supported this idea ·
-
22 votes
TechSupport247 supported this idea ·
-
2 votes
TechSupport247 commented
I believe this refers to the change which will make Windows PowerShell the default in the Windows key+X menu, whereas the conventional command prompt was the old default.
-
37 votes
TechSupport247 supported this idea ·
-
38 votes
TechSupport247 supported this idea ·
This issue has been around as long as the attribute editor tab. :(