Jump to content

cheshireguy

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

5 Neutral

About cheshireguy

Personal Information

  • Location
    Shrewsbury
  1. We have just moved to Exchange 2013 from Exim. By default any devices using active sync that can support wipe get a message saying the administrator has the power to wipe this device. As a Sys Admin I think this is brilliant however all our staff and management team are up in arms. How dare IT have this power "turn it off immediately" I know data protection etc etc Does anyone know how to disable remote wipe on Active sync in 2013 - PS commands gladly accepted, can't find anything on the web. Cheers Marcus
  2. Checked with the MAC today all seems well. We don't have a MAC server or boot camp/parallels etc. The trick I posted above does seem to be working Open Terminal Sudo vi /etc/ntp.conf change server to server your time server Make /etc/ntp.conf unchangeble: sudo chflags uchg /etc/ntp.conf Edit the /etc/hostconfig must be edited to contain: TIMESYNC=-YES- Save and close out of terminal Ensure in preferences on date and time that the use time server is ticked - don't worry which Apple server it points to that is irrelevant. Wne I get 5 mins I will post the proper process but I want to check it works over a longer period
  3. OK - over the weekend, the time did slip, however I have found another bit of info which seems to set the ntp.conf file and fix it. NTP Clients Again the following should be done in the described order. On Mac OS X Clients and on those Mac OS X Servers that are to act as NTP clients (that means they query a time server but do not answer NTP queries) the following needs to be done: In System Preferences ("Date and Time" pref pane) "synchronize time automatically" must be ticked; then the first tab of this pref pane must be activated and the window left open. Then in Terminal a time server to sync with must be added to /etc/ntp.conf like so (as to finding the right time server see above): server mein.zeitserver.de prefer iburst minpoll 12 maxpoll 15 Now /etc/ntp.conf must be saved and made unchangeble: sudo chflags uchg /etc/ntp.conf After that the System Preferences can be closed. On a Mac OS X Client that is all. On a Mac OS X Server the file /etc/hostconfig must be edited to contain: TIMESYNC=-YES- Still working on it
  4. At the end of the day it all comes down to config files. Looks like you can't edit the ntp.conf file because after a reboot it reverts same with loads of other ntp and ntpd file which I have tried to hack. However I have changed the hostconfig file to read in /etc to read TIMESYNC=-YES- I then restart the ntp service and the time changed to the correct time. To be honest not sure what has happened, me thinks I have stop it using NTP so it has reverted to it's Hardware Clock - which is obviously right. I may be completly wrong, however it seems to be working - watch this space. Going to join the machine to AD and we'll see;)
  5. Tested and working - DOH!!!, I am slowly warming to Windows 7 but still finding querks. Cheers for the help
  6. Cheers - fast user switching is disabled, will give that a go cheers
  7. Dear All I apologise if this is a repeated post but I have had a quick search and cannot find anything. I am really concerned that if a user locks there computer there is no way of logging them off at the console like you could in XP. Does anyone have a fix for this? I know I could use psexec but to be honest if a teacher locks a workstation leaves it and then someone else needs to unlock it, it would be much easier for them to do it themselves. Any thoughts on this bug gratefully excepted.
×
×
  • Create New...